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

@metalab/generator-webpack

v0.4.2

Published

Setup webpack for your project.

Downloads

3

Readme

generator-webpack

Scaffold common webpack patterns.

npm install -g @metalab/generator-webpack
# Setup webpack proper.
yo @metalab/webpack
# Create your first entry.
yo @metalab/webpack:entry
# Build the entry you just made.
npm run build:name

Sub-generators

  • babel - Add support for ES6.
  • build-info - Inject a build-info module.
  • compatibility - Add support for older versions of IE.
  • env - Import environment variables into your apps.
  • entry - Generate a config for an entrypoint.
  • external - Bundle an external resource.
  • hot - Hot module reload magic.
  • json - JSON/JSON5 support.
  • optimize - Enable UglifyJS support for production builds.
  • postcss - Add support for postcss stylesheets.
  • progress - Show progress info as webpack build goes on.
  • root - Make another folder act like node_modules.
  • sass - Add support for SASS stylesheets.
  • sharp - Image pre-processing with sharp.
  • source-maps - Add sensible source-map support.
  • stats - Generate a stats.json file.
  • vendor - Bundle common code into a vendor.js file.

The webpack structure is setup as follows:

+ config
 + webpack
  + partial
   - babel.webpack.config.js
   - sass.webpack.config.js
   - ...
  - entrypoint-1.webpack.config.js
  - entrypoint-2.webpack.config.js
  - ...

Other thoughts:

  • https://www.npmjs.com/package/git-sha-webpack-plugin
  • https://github.com/huston007/webpack-config-merger
  • https://www.npmjs.com/package/webpack-graph
  • https://github.com/deepsweet/autopolyfiller-loader