-
Notifications
You must be signed in to change notification settings - Fork 14
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 would loader hooks/extensions/plugins leverage this? #11
Comments
also of note, if using
|
|
Currently So I guess this theoretical loader does its work before Node tries to resolve these references, so Node doesn’t know the file paths to pass to the loader. But Node could perhaps load |
@GeoffreyBooth The issue would be redirecting the {
"exports": {
"/package.json": "./run-random-code-to-generate-data.mjs"
}
} |
Also, for additional context: The |
If I'm writing a custom resolution algorithm, will there be a way to still leverage this behavior? Let's say I resolve to a package mapped to non-
file:
URLs. How do I still allow that package to specify exports?The text was updated successfully, but these errors were encountered: