npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@stoplight/webpack

v2.6.0

Published

Webpack helpers, built on top of webpack-chain.

Downloads

34

Readme

Webpack Helpers

Maintainability Test Coverage

Plugins, built around webpack-chain, that make creating webpack configs easier.

Plugins

  • BrowserFS: Replace the native fs module with the BrowserFS equivalent.
    • Note: must yarn add browserfs in your project if using this plugin.
  • Bugsnag: Upload sourcemaps to bugsnag.
  • CSS: Import css.
  • Fonts: Import fonts.
  • HTML: Render an html template.
  • Javascript: Parse javascript.
  • Monaco: Import monaco.
    • Note: must yarn add monaco-editor in your project if using this plugin.
  • Optimizations: Minification, chunks, etc.
  • Presentation: Better terminal output.
  • Public: Use a public assets folder.
  • Serve: Serve up a hot reloading dev environment.
  • Stylus: Import stylus.
  • Typescript: Parse typescript (and optionally also javascript).
  • Web Workers: Import web workers.

Installation

# latest stable
yarn add -D @stoplight/webpack

Usage

In your webpack.config.ts file:

import { createConfig } from "@stoplight/webpack";
import * as path from "path";
import webpack from "webpack";

import { buildEnv } from "./env";

const isElectron = process.env.RUN_CONTEXT === "desktop";

const config: webpack.Configuration = createConfig({
  srcDir: path.resolve(process.cwd(), "src"),
  distDir: isElectron
    ? path.resolve(process.cwd(), "desktop", "src", "dist")
    : path.resolve("desktop", "src", "dist"),
  publicDir: path.resolve(process.cwd(), "src", "public"),
  isElectron,
  analyze: false,
  debug: false,
  stats: undefined,
  plugins: {
    browserfs: isElectron ? undefined : {},
    bugsnag: undefined,
    css: undefined,
    fonts: {},
    html: {
      // string to assign to the head title tag
      title: "Stoplight Studio",

      // object to assign to window.env in a head tag script
      env: buildEnv(),

      // string of html to be inserted towards the top of the head tag
      metaHtml: "",

      // string of html to be inserted towards the bottom of the head tag
      headHtml: "",

      // string of html to be inserted towards the bottom of the body tag
      bodyHtml: ""
    },
    javascript: undefined,
    monaco: {},
    optimizations: {},
    presentation: {},
    public: undefined,
    serve: {},
    stylus: undefined,
    typescript: {},
    workers: undefined
  },
  onBeforeBuild: _config => {
    // ...do whatever you want w config, which is an instance of webpack-chain
  }
});

export default config;

Contributing

  1. Clone repo
  2. Create / checkout feature/{name}, chore/{name}, or fix/{name} branch
  3. Install deps: yarn setup
  4. Make your changes
  5. Run tests: yarn test.prod
  6. Stage relevant files to git
  7. Commit: yarn commit. NOTE: Commits that don't follow the conventional format will be rejected. yarn commit creates this format for you, or you can put it together manually and then do a regular git commit.
  8. Push: git push
  9. Open PR targeting the develop branch