Evan Wallace

You have encountered "tree shaking" also known as "dead code removal." There is no observable difference between this code: ```js (() => { function sum(a, b) { return a +...

Oh, interesting. That's pretty cool. I didn't know about that feature of Parcel. I assume this also works for the `SharedWorker` constructor. You should be able to get this to...

> It works but uses a rather ugly hack to pass both the importer path and the imported file's path to be onLoad handler which makes me think there must...

I was assuming that the `new URL('./some/file.js', import.meta.url)` syntax should cause a new JavaScript entry point to be created independent of whether there is `new Worker` nearby or not. The...

Thanks for the report. I just checked and this is not a recent regression (I suspected #1591). I can reproduce it when compiling files one-at-a-time but not when bundling, so...

Sorry, esbuild's plugin API is intentionally designed to be accessible via JavaScript instead of the CLI. IMO using JavaScript is much more intuitive and ergonomic than a CLI for complex...

I believe the interpretation as CommonJS may be due to the use of `external: ["./node_modules/*"]`. I was able to get your code to work by making `@aws-sdk/client-s3` external explicitly. See...

By `raw request path` it sounds like you're asking for the original (pre-resolve) import path instead of the calculated (post-resolve) import path. Is that correct? For example, in the following...

Yes, this is currently a limitation of the plugin API. One problem is that esbuild's internals read this information in the resolver for performance, but this does not make for...

Just got a chance to look into this. It looks like it works with the CLI and Go APIs but not with the JavaScript API because the JavaScript API is...