Vote what you want the Webpack team to focus on

We wanted to give influence to those who are involved in open source and contributing to the community. Would be happy to discuss alternative options.

I have heard Instagram login is in the works. You might be able to login after all ( ͡° ͜ʖ ͡°).

hey, you're a meme now https://imgflip.com/i/1ep7b0

I checked out speedread, but then I saw I had to create yet another account at which point I lost interest.

Here are the things I had the most trouble with in the beginning:

- Externals. I still have trouble wrapping my head around this directive.

- Multiple output paths for multiple entry points (it wasn't intuitive to make the entry point key a relative path and I had to discover this method on stack overflow).

To be fair, a proper set of documentation for webpack would be a several hundred page book.

Edit: I see my second point still isn't mentioned anywhere in the old or new docs. Specifically:

  const ExtractCSS = new ExtractTextPlugin('[name].css');
  ...
  entry: {
    ['./app/bundle']: './source/app/index.js',
    ['./admin/bundle']: './source/admin/index.js'
  },
  output: {
    path: './build/',
    filename: '[name].js'
  }
  ...

would create:

  build/
    app/
      bundle.js
      bundle.css
    admin/
      bundle.js
      bundle.css

Wow. This documentation is so much better than what was previously available. Thank you from the bottom of my heart.

The one thing I will point out is that from a UX perspective the font you are using "Cabin", is naturally smaller and more compact than more common sans fonts (e.g. Open Sans, Century Gothic).

Because of this, even though your site is font-size 16, everything appears smaller than it would normally be.

I had never seen this before. I'm excited to explore it, as I use webpack for all my projects anymore. Thanks you.

Thanks so much for the pointer to that plugin; it looks like it does exactly what I'm looking for. It's a testament to webpack's configurability that a plugin can get deep enough into the guts to do that. I remember looking at https://github.com/webpack/webpack/issues/250 ("Cache build information between webpack processes") back in the day and even now it looks like it's still open/unresolved/tagged "difficult."