Bradley Farias

I'm fine with it being punted, just recording and pointing that this needs to be worked on eventually.

cross referencing relevant issues: - Per package loader hooks: https://github.com/nodejs/node/issues/18233 - this basically would enable packages to produce a scope in which loaders are applied. It is actually important that...

there is an upcoming PR that implements this functionality and has a test case that allows replacing the global specifiers resolution https://github.com/nodejs/node/pull/39240 ; the JS spec itself does not allow...

@DerekNonGeneric I at least in the Loaders side of things don't see the need for URLPattern or even the advantage to using it. For example, if we scope things using...

Service Workers use cases seem a fine to hope they match, but various things like having a HTTP cache implementation as the means of controlling things like `file:` URLs likely...

@guybedford the main usage is to be able to resolve a dependency, not to actually force that dependency to be loaded. Indeed the dependency may never be loaded depending on...

IDK about web spec nor do I really have much investment due to my social position regarding modulepreload; tooling, such as preloaders or bundlers, could use it without requiring partial...

I have slight reservations about the right hand side of the operator being a dynamic variable lookup in a syntax that doesn't look like it is. In property access and...

The problem with dynamic evaluators is ahead of time tooling can't use it easily and likely won't have guarantees about parameters being stateful. I think we don't need to decide...

If you use --loader on a single threaded application that is somewhat true but shouldn'tbe 2x. Plenty of stuff like v8 intrinsics, c++ code, etc. are not recreated. If the...