Evan Wallace

> @evanw in https://github.com/evanw/esbuild/blob/a6c42a19ff62a70d118e8e016a302fcac84ed95f/CHANGELOG.md#0150 you noticed `over a 10x speedup (3.4s to 0.24s)`, do you still see those improvements? Yes I do, but I suspect you are running esbuild in...

From [this comment](https://github.com/evanw/esbuild/issues/1983#issuecomment-1029805127) it sounds like Yarn 4 might also change the data format: > I'm considering switching to a pure JSON format in the next Yarn major (and we'd...

I'm closing this issue as "won't fix" for the reason described above.

A fix for this has landed in master, so I'm closing this issue as fixed.

I'm guessing what's happening here is that something on the page is using AMD and `window.define` exists. Since esbuild only supports ESM and CommonJS as input, it doesn't make any...

I'm closing this because the API mentioned above has since been deprecated in favor of something else. We can consider this if a relevant API is ever made stable.

I'm closing this issue because I'm not planning on doing this. For what it's worth esbuild has since added native support for Yarn PnP, so the concern in the original...

This isn’t straightforward on esbuild’s side because the CLI is native code and doesn’t contain a JavaScript interpreter. This feels like something that sounds be fixed on AWS’s side instead....

After the original comment for this issue was posted, esbuild exposed a `resolve` API to plugins that I believe could be used by this plugin to handle this case: https://github.com/evanw/esbuild/releases/v0.14.8....

Closing this issue due to lack of a follow-up reply.