Geoffrey Booth

> @bmeck @MylesBorins could either of you speak to the impetus for this? Pros and cons here: https://github.com/nodejs/modules/issues/351#issuecomment-634347749

I agree that we should find answers to those questions. I would hold off on adding it to the TSC agenda until we have those answers.

There's also a potential benefit in moving non-custom loading off-thread as it would protect internals from prototype pollution (I think). That would argue that we should make this same refactor...

I have hesitations about this. We can’t and possibly won’t ever be able to clear the ESM cache, because the modules are loaded into V8 and V8 doesn’t provide an...

Something else discussed in https://github.com/nodejs/node/pull/44250 that we should consider is making new subpath additions (like any other core module getting `/promises`) allowable as semver-minor. This might be a code change,...

> I think we’ve discussed the issue enough time that we should move to a vote on this specific issue relatively quickly. The vote might be if this PR can...

@mcollina My recollection of the outcome of `node:test` was that initially there was a desire to have the new module be unprefixed, which meant that `test_runner` was the best available...

> Since people did not specify a family, we can assume they have no preference (and it is optional in the RFC) and therefore we can skip those options for...

> If a node app uses the worker threads API to launch worker threads, does each get its own loader thread? I think the current state (before this PR) is...

> we need the loader hook API to stabilize It’s pretty close. Once https://github.com/nodejs/node/pull/44710 and https://github.com/nodejs/node/pull/43772 land and we allow some time for baking, that’s all that’s on our list...