Bradley Farias

I agree if we are talking about multiple sources that maybe be true. However, my point that this enables a mode in which early errors being deferred / not early...

As an examples: If you strip local binding names to be non-string based. Errors like `eval`/`arguments` being invalid identifiers can no longer occur. If the AST doesn't support `with`, that...

@kannanvijayan as mentioned earlier changing an Early Error to `throw` breaks the semantics and invalidates your earlier desire: > We want a bijective mapping (up to the semantic equivalence guarantees)...

I would disagree on "semantics are exactly equivalent" if execution differs.

Can you instrument PnP at all? I thought the loader it produces couldn't be instrumented?

In newer builds of v8, code coverage is built in. I would say looking at https://chromedevtools.github.io/devtools-protocol/tot/Profiler/#method-startPreciseCoverage first might be the quickest approach. Web compatible hooks for ESM are still being...

~workflow: 1. `node --inspect-brk=$DEBUG_PORT app.js` 2. connect over `http://127.0.0.1:$DEBUG_PORT/json` to grab URL to send messages to over `ws:` 3. `Profiler.enable` 4. `Profiler.startPreciseCoverage` 5. `Runtime.enable` -> should generate a `Runtime.executionContextCreated` with...

`esModuleInterop` won't solve all the relevant concerns and would cause potentially more confusion unless well documented. Lots of docs around how `default` behaves different from native Node ESM would be...

I'd note that `import.resolve` would expose potential resolutions that might be prevented in other contexts. ```js // name: privileged // file allowed to resolve 'secret' export function resolve(foo) { return...

@mathiasbynens since IO is part of Node's bottlenecks sometimes I think we would want it to some extent, even if skewed / needing to plaec timers on start/end of every...