Bradley Farias

> For inter-module communication I'd prefer if we could use modules as the communication channel. I'm unclear on this idea. > I'm not sure if ping-pong over the loader is...

@jkrems I think thats a bit awkward but understand the idea. I still think they need a synchronous communications channel with the preload code and if such a thing existed...

@apparebit please open a different issue if you want to discuss deleting modules. Currently V8 does not have any lifecycle hooks for module lifetimes and modules are increasingly aiming towards...

I think the only thing I might want is more tests for Subpaths really. Should probably split that up into much more granular topics (exports, imports, conditions, patterns, require() [no...

This issue would have to deal w/ CLI arguments potentially from https://github.com/nodejs/node/issues/37848

@ljharb because it adds consistency and I cannot think of a reason to disallow these specifiers on concrete concerns if we are not reserving them for future features. Any future...

@ljharb why is it a footgun? is there clear reasoning here or is it just a linting issue?

@ljharb that statement is true for any given one off script that isn't installed via a package manager and uses bare specifiers for things. I do see utility in various...

@ljharb the file specifiers are URLs, not paths, they do have fragments taken into consideration.

@ljharb people are using this preservation of URL aspects for things like cache busting or ferrying meta-data already, it isn't something we can decouple. [see docs](https://nodejs.org/dist/latest-v14.x/docs/api/esm.html#esm_url_based_paths)