Support TS node16, nodenext and bundler module resolutions #2400
Conversation
This file contains 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
Support TypeScript node16, nodenext and bundler module resolutions.
|
Aims to resolve #2307 |
JamesLMilner
approved these changes
Feb 26, 2023
twelch
approved these changes
Feb 27, 2023
evgenyt1
changed the title
|
Thanks @evgenyt1 ! 👍🏻 |
|
@JamesLMilner any idea when this will be released? |
|
@markcarroll & others - 
|
This was referenced Apr 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently
@turf/turfdoesn't support modern node16, nodenext and bundler module resolution strategies of TypeScript.When "exports" is defined in
package.json, a custom conditiontypesshould be added there as well.More on moduleResolution
Also info on TypeScript's package.json Exports, Imports, and Self-Referencing