Evan Wallace

Metadata for both input files and output files is accessible with the `metafile` feature: https://esbuild.github.io/api/#metafile

The `entryPoint` property was added to the metafile in [version 0.8.51](https://github.com/evanw/esbuild/releases/v0.8.51). I believe using that should be sufficient to address this: ```diff const result = esbuild.build({ entryPoints: { 'out/pageA': 'src/pageA',...

In the past I have thought about adding a plugin callback for when a file is emitted, which is sort of like what you're asking for. It would run after...

> For hashing purposes Hashing is kind of complicated because of import cycles. Heads up that I am currently planning to use the algorithm described here: https://github.com/evanw/esbuild/issues/518#issuecomment-781818245. Each output file...

> Make the metafile's input and output paths relative to something that can be explicitly set. I'd probably say the `Outdir`. It should probably be relative to [outbase](https://esbuild.github.io/api/#outbase) instead of...

Sorry, top-level await is not supported. It messes with a lot of things and adding support for it is quite complicated. It likely won't be supported for a long time.

Right now there is an equivalence in esbuild between CommonJS modules and ES6 modules. A module can be written in either syntax and can even mix both syntaxes. That no...

I'm planning to add pass-through support for this now that [node is enabling it by default](https://github.com/nodejs/node/pull/34558). It won't work while bundling but it will still be useful for certain use...

> Is the situation for this still the same? Yes, top-level await still doesn't work with bundling.

TLA is so complicated. I'm still trying to figure out how to support it but it has been really challenging. I'm trying to match all of the real evaluation order...