-
Notifications
You must be signed in to change notification settings - Fork 71
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
How do we install package name maps? Node.js context #15
Comments
This proposal doesn't (currently at least) cover automatic extensions or searching for modules in multiple directories. Node might want to extend this proposal with their own custom properties, but I hope they don't! cc @bmeck for his thoughts here. |
Given that we have loader hooks I would probably suggest we leave this up to a userland loader for some time. cc @nodejs/modules |
I don't think the proposal will ever cover searching, that's something we need to actively avoid. |
Let me close this, as the spec won't be the one deciding this, but instead the Node.js team. Perhaps @guybedford or @MylesBorins know the right place to direct @caub to see where any ongoing discussions are happening? |
Does Node.js need additional configuration? can it be in
package.json
?If I understand well, this proposal may cover webpack's custom resolvers and aliases? and the possibility to have internal import 'bindings' like:
I've often things like
that would benefit being standardized. Since it's needed by test engines and linters also
The text was updated successfully, but these errors were encountered: