V2: Remove Node10 subpath fallbacks #804
Merged
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.
Active support for Node.js v10 ended nearly four years ago, security support ended nearly three years ago. I think we can safely remove the fallback for subpath exports in v2.
For context, see #802.
We still maintain the package.json field
typesVersions
so that TypeScript can see types with Node10 module resolution (it's still commonly used with the aliasnode
). But there doesn't appear to be an obvious reason to maintain JS files for runtime purposes.