This repository was archived by the owner on Mar 10, 2023. It is now read-only.
feat: typescript 3 -> 4 #127
Open
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Move from compiling on typescript 3.9 to typescript 4.3.
This is annoying me as it means we end up with a production dependency of 3.9, instead of the 4.3 we're using locally. I have no idea how this is ending up as a production dependency, but it is! Thanks yarn. Tharn.
Note that typescript aren't great at semver; 3.8 -> 3.9 is the same level as change as 3.9 -> 4.0 and 4.1 -> 4.2, etc.
That is, this isn't a huge breaking change.