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 is an old Node.js pattern whereby a require('pkg/') import style is permitted to resolve.
require('pkg/')
if trying to support such a map in import maps via:
{ "imports": { "pkg/": "/path/to/pkg/index.js" } }
the browser console gives the error:
Ignored an import map value of "a/": Since specifierKey ended in a slash, so must the address: /a.js
If such a pattern were to remain used in Node.js ES modules, it might make sense to still consider supporting these cases resolving. //cc @hiroshige-g
The text was updated successfully, but these errors were encountered:
Dupe of #244 ?
Sorry, something went wrong.
Ah thanks, yes closing. Wdyt re progress there? I'm tempted to consider proposing Node.js ban all trailing slash resolutions otherwise for ESM.
Yeah, I don't think we have any new information that would change the calculus over there...
No branches or pull requests
There is an old Node.js pattern whereby a
require('pkg/')
import style is permitted to resolve.if trying to support such a map in import maps via:
the browser console gives the error:
If such a pattern were to remain used in Node.js ES modules, it might make sense to still consider supporting these cases resolving. //cc @hiroshige-g
The text was updated successfully, but these errors were encountered: