fix(node-resolve): bump is-builtin-module version, imports with a trailing slash #1424
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.
Rollup Plugin Name:
node-resolve
This PR contains:
Are tests included?
Breaking Changes?
List any relevant issue numbers:
#1211
Description
Adding a trailing slash to a module name in an import statement is the convention for telling node to use the local module with that name, rather than the builtin module with the same name.
For an example, see the docs for punycode which is available as both a builtin and standalone module for node.
The is-builtin-module package did not respect this convention. A fix was made and released in is-builtin-modules v3.2.1. This change bumps the version of the dependency and adds a test case to verify that import statements with a trailing slash are not treated as builtin modules by the node-resolve package.