Joyee Cheung

cc @nodejs/platform-s390 it only fails on s390 it seems

Manually started Jenkins CI for @anilhelvaci since the last commit does not have an approval (I took a look at the test and I think it's safe to test them....

handling multiple calls from the Node.js side SGTM.

After some thoughts I think the higher level `requires()`/`link()` hooks that span across `resolve`/`load` make more sense than lower level `exports()`/`link()` hooks that run after `load` because they are more...

> Then if I also want to register my instrumentation library, and it uses requires/link, do the CoffeeScript hooks never get called because they’ve been bypassed? Or are you suggesting...

After attempting to prototype the high-level wrappers in the ESM loader I realized that there are some nuances in the current design - the `nextLoad` and `nextLink` (or similar) in...

> How does that work for loaders that are prerequisite for subsequent loaders to work? For example let's say a TS loader needing to resolve & load files from within...

> The alternative is to provide the DeasyncWorker we talked about, and use it to implement a synchronous http client we use for this. In the end that's what we...

> Would it make sense to have a think like the "link" hook that works for both module formats? I don't think so, because this is where one of the...

> Like if you allow the CJS side to see what the export names are without directly accessing them you could do a similar "replace when available" kind of semantic...