Eduardo Bouças

> > this is technically a breaking change > > are we planning on doing a major bump? or do we expect people to read the patch notes carefully? We'll...

Hi @bram-l! Thanks for raising this and apologies for the slow response. The esbuild PR you linked would indeed solve this issue, and I think it'd be the best course...

I think we should keep the old version of `@babel/parser` for the time being, unless we find a strong reason to upgrade (like a bug or a missing feature).

Hi @PH4NTOMiki. Can you please confirm: 1. Are you deploying via the Netlify CLI (i.e. using `netlify deploy`) or using the CI flow? 2. If you downgrade to version 9.7.0...

Also, can you clarify what routes are giving you that runtime error? I've deployed your reproduction case to https://62176ba95237e4afd8500e35--eduardo-tests.netlify.app/ and I haven't been able to reproduce the error yet.

Thanks for the additional info! We're looking into it and we'll keep this issue up-to-date with any progress.

Hi @zoexx. Apologies for the late reply. We're currently working on a solution to allow tapping into esbuild's `define` via a configuration property, just like you described. I'll update this...

> Any other plugins/settings we would like to configure for our users? Worth noting that esbuild plugins carry a performance penalty, which can be pretty significant depending on the plugin....

Thanks for your input, @spencewood! We're currently working on adding this configuration option, with an API surface that looks very similar to the example you shared. We'll make sure this...

> > It would be nice (critical if the old bundler is going away) to be able to accomplish this in some way, either through simply including raw, non-js files...