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

As a developer I want to resolve conflicts between node's internal packages and npm packages #2315

Open
mor-n4 opened this issue Feb 17, 2022 · 1 comment

Comments

@mor-n4
Copy link
Contributor

mor-n4 commented Feb 17, 2022

There are name conflicts between node's internal packages (e.g. "fs", "path", "url", etc.) and certain npm packages available from npmjs.org.

For example: "url".

We need a way to allow an N4JS project to use both node's internal package and the npm package with the same name.

Node provides the following special module specifier syntax to resolve such conflicts:

import * as url1 from "url" // will import from package "url" in the node_modules folder
import * as url2 from "node:url" // will import from node's internal "url"
@mmews-n4
Copy link

mmews-n4 commented May 4, 2022

probably fixed by GH-2341

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants