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 alias node). But there doesn't appear to be an obvious reason to maintain JS files for runtime purposes.
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
typesVersionsso 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.