FYI: Phoenix drops webpack and npm for esbuild

Summary

Phoenix is replacing its use of Node, npm, and webpack with esbuild, a Go-written JavaScript bundler, in the upcoming Phoenix 1.6 release. The change responds to support burden and reliability problems: the post says npm, webpack, or brunch were involved in roughly 30% of Phoenix’s reported issues, while node-sass and npm v7 had recently broken phx.new. esbuild compiles to native code, handles common asset-pipeline tasks, and is intended to provide newcomers with a seamless setup and long-term users with more reproducible JavaScript and CSS builds. Teams doing substantial frontend JavaScript can still use customized webpack or other tooling, while esbuild remains an opt-in path for complex client-side work. Existing projects can use Phoenix 1.6, although the post notes possible zombie processes and says migration snags remain to be assessed.

Takeaways

1. 1

   Phoenix issue counts cited in the post were 591 involving npm, 79 involving webpack, and 171 involving brunch, with overlap bringing the estimated packaging-related share to around 30%.

2. 2

   esbuild is written in Go and compiles to native code, providing a fast JavaScript bundler for common asset-pipeline tasks without making Node tooling the default.

3. 3

   The migration does not block custom frontend setups, but the post warns that esbuild could leave zombie processes until an upstream pull request is merged; migration issues were still being evaluated before release.