4 ms·

The document seems to have gotten a little better, lot better than Webpack 1, however the plugin ecosystem is the most frustrating part imo. Webpack gives plugi

by shriek 9y ago

The document seems to have gotten a little better, lot better than Webpack 1, however the plugin ecosystem is the most frustrating part imo. Webpack gives plugin creator some form of freedom and because of that, and the lack of types in JS, you're at the mercy of proper docs on the plugins you're relying on. Either that or go through the source code to find out what the heck is even accepted as options.

thelarkinn 9y ago
We heard this feedback infact and we wrote the entire plugin system for webpack 4! (https://github.com/webpack/tapable https://github.com/webpack/tapable). Take a look at the only PR open which is us working to provide the best Type system possible for our new API (which was infact designed to support it). Even better is that you can find all the "hooks" on an instance by doing `compiler.hooks` so now you get a far better authoring experience :-D
- jblg 9y ago
  Would be better if Webpack had defaults that just worked out of the box without configuration.
- shriek 9y ago
  That's awesome. I haven't played with webpack 4 yet. Just recently started playing with webpack 3. I'd be keeping an eye on it.