Fix TypeScript type imports #6
Merged
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
TypeScript 4.7 includes the new `node16` module resolution value. This requires imports to have an extension, even if the import doesn’t reference an existing `.js` file. This still works with other module resolution values.
github-actions
bot
added
👋 phase/new
ChristianMurphy
approved these changes
Jul 11, 2022
wooorm
approved these changes
Jul 11, 2022
This comment has been minimized.
This comment has been minimized.
|
Released in 2.0.2! |
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.
Initial checklist
Description of changes
TypeScript 4.7 includes the new
node16module resolution value. This requires imports to have an extension, even if the import doesn’t reference an existing.jsfile.This still works with other module resolution values.