Geoffrey Booth

> @GeoffreyBooth Exactly, the way the `fileURLToPath` is used today, simply don’t worth exposing the C++ version. Okay, so then should we close this PR? Is there something else of...

Are you sure it’s not just that named exports aren’t found, but rather that the source is undefined? See https://github.com/nodejs/loaders#milestone-2-stability:~:text=Support%20loading%20source%20when%20the%20return%20value%20of%20load%20has%20format%3A%20%27commonjs%27

> It’s interesting because it doesn’t work `--loader` in the worker’s `execArgv`, but it works fine if `--loader` is passed to the main script (the worker inherits the flag). I...

> the loaders docs do claim that they follow the pattern of `--require` Only in the sense that the way that chaining works for multiple invocations of `--require` is the...

> I guess my question is, are there actually technical reasons why this can’t be implemented? In the current behavior, there’s a loaders thread and it works for both the...

> I still think allowing to provide a custom loader for each worker is very useful for all sorts of use cases What would a specific use case be? When...

> I believe that would work for my use case. What is your use case? > CLI tools can’t really set Node.js options. We’ve been discussing adding support for `.env`...

> Using loaders in a worker without requiring users to specify CLI flags. Can you explain a bit more? Is this a CLI tool? What does it do? Why does...

> The loader itself is just used for hot module reloading, so I think `registerLoader()` will work just fine. If you find a good general solution for hot module reloading,...

> This boils down to essentially the same algorithm that node-glob used until the recent rewrite So . . . why wouldn’t we just import the latest version of `node-glob`?