Mention experimental specifier resolution in TypeScript recipe #2910
Conversation
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
|
fixes #2593 |
|
Thanks for the PR @rrichardson! I'd like to make some edits (nothing worth a back-and-forth over), hopefully I'll get to that over my break at the end of the year. |
|
I've edited this so we stick a little closer to the default behavior, but still allow people to discover these experiments. |
novemberborn
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Using the nodeArgument
--experimental-specifier-resolution=nodemakes it so one you don't have to add the.jsextension to files when importing for your tests. (Such things are not feasible for people with large typescript workspaces)This PR just updates the typescript recipe to suggest such a change.