-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
module: change default resolver to not throw on unknown scheme #47824
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
Merged
nodejs-github-bot
merged 12 commits into
nodejs:main
from
giltayar:default-resolve-no-throw-scheme
May 19, 2023
Merged
Changes from 1 commit
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
52d276e
module: change default resolver to not throw on unknown scheme
giltayar 94afcae
fix lint errors
giltayar c87c78c
Update doc/api/esm.md
giltayar 3df4003
added test for extensions, and simplified protocol test
giltayar f615248
remove fixtures by inlining them in the test
giltayar e4b4cdf
change load example to "import map" semantics
giltayar a387b9c
fix lint errors
giltayar 88a4ce9
Update doc/api/esm.md to improve "import map" loader
giltayar b0eb1c0
Document resolution not failing on url protocol
giltayar 98924dd
add some loader info to esm docs and change to "default resolver"
giltayar 357e8db
esm.md fixed based on comments
giltayar 2c7e695
fix expected error message
giltayar File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Update doc/api/esm.md
Co-authored-by: Geoffrey Booth <[email protected]>
- Loading branch information
commit c87c78c16c7404d692e837ed1eeea487938f56bf
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you tested this code? Can you add it to the examples in https://github.com/nodejs/loaders-test?
We should probably have an example that needs to use both
resolveandload, so that we demonstrate how the two hooks work together. Ideally it would be as realistic a use case as possible.Speaking of realistic examples, another “
resolve-only” use case discussed in the design docs for the loaders API was to rewrite specifiers likelodashinto URLs likehttps://esm.sh/lodash. Perhaps this might be a better example than this “overriding loader,” as it would presumably be a lot shorter of an example.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have (in my repo that I link to in the issue), but I can definitely copy it to https://github.com/nodejs/loaders-test.
The example I gave is very realistic as it is a simplification of import maps, where you can map bare specifiers to specific files. I can definitely use your use-case, but I think in terms of complexity, they're roughly the same.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once this lands (hopefully...😊), I'll not only add this loader to the
loaders-test, but also modify thehttp-loaderandtypescript-loaderto not need resolvers.