Skip to content
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

Closed
caub opened this issue Mar 16, 2018 · 4 comments
Closed

How do we install package name maps? Node.js context #15

caub opened this issue Mar 16, 2018 · 4 comments

Comments

@caub
Copy link

caub commented Mar 16, 2018

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

	resolve: {
		extensions: ['.js', '.json'],
		modules: ['src', 'node_modules'],
		alias: {
			assets: `${__dirname}/assets/`,
		},
	},

that would benefit being standardized. Since it's needed by test engines and linters also

@matthewp
Copy link

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.

@bmeck
Copy link

bmeck commented Mar 16, 2018

Given that we have loader hooks I would probably suggest we leave this up to a userland loader for some time.

cc @nodejs/modules

@justinfagnani
Copy link
Collaborator

This proposal doesn't (currently at least) cover automatic extensions or searching for modules in multiple directories

I don't think the proposal will ever cover searching, that's something we need to actively avoid.

@domenic
Copy link
Collaborator

domenic commented Jul 3, 2019

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?

@domenic domenic closed this as completed Jul 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants