Guy Bedford

An API for unloading modules certainly makes sense. Usually with a direct registry API there is the tracing issue. An API that handles dependency removal can be useful. A simple...

@A-lxe thanks for opening this discussion. It was interesting to hear you say that multiple loaders were one of the features you find important here. The PR at https://github.com/nodejs/node/pull/18914 could...

@A-lxe agreed we need a way to chain loaders. Would the approach in nodejs/node#18914 work for you, or if not, how would you want to go about it differently? One...

> Why is there no runtime api for registering loaders? Loaders are a higher-level feature of the environment, kind of like a boot system feature. They sit at the root...

Great to see work moving here! I really like the overall model, we maybe just have a few disagreements about the exact APIs. I’ve already statement my feedback in the...

> Per "separation". I agree there needs to be a "fetch"/"retrieve" hook of some kind, but not that resolve` should not be able to return a body. The problem you...

> Is the concern reading the file, or evaluating the file. I would be surprised if the loader actually evaluated the file. The concern is reading the file - doing...

@devsnek does dynamic import not work in the current loader at all? That does sound like a possible bug to me. @bmacnaughton the loader hooks are still under development and...

Ah right so it’s the promise deadlock case. Yes so the solution is readdressing the original source load (‘?original’ type resolving, where an opt-out breaks the circularity). On Mon, Nov...

Layered addressing becomes very tricky to manage and I don’t tend to like the idea of loader access levels but it could be an alternative yes. On Mon, Nov 4,...