This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.js...
@rauschma Confused as to why that note about semver at the top of the release notes is needed. Are people really doing `esbuild: "*"` and then complaining when it breaks?