We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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"
The text was updated successfully, but these errors were encountered:
probably fixed by GH-2341
Sorry, something went wrong.
No branches or pull requests
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:
The text was updated successfully, but these errors were encountered: