-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom module loader for Workers #21667
Comments
/cc @nodejs/modules @nodejs/workers |
@rumkin the overall idea sounds good but i think we need to wait a bit to figure out how loader hooks will behave in the future. there's a lot of movement with them at the moment. |
I tend to agree with @devsnek in that I like the idea and think this is too early and it should be addressed once modules settle. Mixing two experimental APIs means they each hinge on each other and cannot progress to stable unless progressing together - this sounds like an enhancement that can happen at a later point. |
There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment. For more information on how the project manages feature requests, please consult the feature request management document. |
There has been no activity on this feature request and it is being closed. If you feel closing this issue is not the right thing to do, please leave a comment. For more information on how the project manages feature requests, please consult the feature request management document. |
Node.js users has two problems:
Workers can solve both of them in very elegant way with custom resolvers which are the same as experimental es module resolver.
It solves sandboxing with full dependency control in custom context. And it simplifies es modules usage with preserving usual code flow in main thread and es flow in worker thread.
/cc @addaleax @TimothyGu @Qard @aqrln @oe @benjamingr @nodejs/workers
The text was updated successfully, but these errors were encountered: