WordPress Replaces Browserify with Webpack for Build Process

During a core JavaScript chat held in May, WordPress contributors agreed on using Webpack (and ES6 imports) instead of Browserify for JavaScript bundling in the build process.

“Since we split the media files in #28510, the core build process has used Browserify to combine the media files,” Adam Silverstein said in the ticket proposing the replacement. “While browserify has served us well, Webpack is probably a better long term choice for the project, especially with the introduction of a new JavaScript framework that may require a build.”

Over the past four months contributors on the ticket have worked on making sure the Webpack setup is working well to build the files. WordPress core committer K. Adam White also reached out to some Webpack contributors for an additional review during the process before replacing Browserify as the JavaScript bundler.

Webpack has rapidly gained popularity among the many utilities for bundling JavaScript files and is one of the most prominent examples of a project that has successfully found a sustainable source of funding through its account on Open Collective. The project funded its first full-time developer through the platform and has an estimated annual budget of $241,650, based on current donations.