Webpack no longer automatically polyfills Node.js APIs. This is a huge breaking change and will inconvenience users & package maintainers.

Webpack no longer automatically polyfills Node.js APIs. This is a huge breaking change and will inconvenience users & package maintainers.

webpack is a module bundler. Its main purpose is to bundle JavaScript files for usage in a browser, yet it is also capable of transforming, bundling, or packaging just about any resource or asset.

For the past couple of years, we have been using require.js for module loading and Grunt for automating tasks on front-end, for one out of…

TL;DR: release planned for 2020-10-10, RC about ~1 month before that. After nearly 1 year of beta testing and about 2 years of development we feel that it's time to release webpack 5 soon. As p…

Webpack architecture is heavily based on events (each plugin is basically a set of event listeners called during compilation). Under the hood, webpack uses a library `called` tapable to encapsulate “publish-subscribe” implementation.

Webpack is becoming the standard in bundling JavaScript, but what does that even mean and how does it work? Let’s find out.

Next.js 9.5 introduces Stable Incremental Static Regeneration, Custom Base Path, Redirects and Rewrites, Webpack 5 Beta, and more!

A gentle introduction to why Webpack exists, what problems it solves, and how to use it.