Wesley Wigham

I license past and future contributions under the triple `MIT OR Apache-2.0 OR Zlib` license, allowing licensees to chose any one at their option.

You'd probably wanna try to make sure your API that's generated is compatible with the one exposed by `@types/mocha`, at least, since once you ship one, it'll override that one;...

Yep. A design decision made a long time ago was that a package's own declarations take priority over declarations from the `@types` namespace - it's more of a fallback than...

> Maybe the TypeScript perf suite would be an inspiration (some info here)? I don't know where it lives though. @weswigham could you help us out here? It's just a...

...?

I'm just someone who contributed a PR once in the past, not a maintainer.

@robpalme 's concern about async-to-execute stuff entering via your dependencies isn't unique to `require(esm)` - TLA is observable in modules in the same way. It's no worse than (or doesn't...

> The syncify in the existing prototype requires the introduction of a separate event loop. Yah, so does `child_process.execSync`. Your point? It's done elsewhere in the node core code. The...

> But it’s not spec compliant with ESM. Promises are specced to suspend main thread. Flattening promises would be non-spec compliant. So problem is lack of work and spec adherence....

Long story short, you point out something you find distasteful with `require(esm)`, and I can probably point out how TLA in modules ends up requiring the runtime do the same...