Update typescript version #108
Merged
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
The previous ^-based version installed 5.2.x automatically, but some changes in 5.2 break the build. I have updated this to explicitly install the latest 5.1 version, one that I have confirmed to work
|
The PNPM lockfile needed updating, which was causing CI to fail. All looks good now, thanks for identifying and fixing this! Typescript's version numbering continues to be one of the great unsolved mysteries of our time... |
lowercasename
approved these changes
Sep 28, 2023
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.
The previous ^-based
typescriptversion string inpackage.jsoninstalled 5.2.x automatically, but some changes in 5.2 break the build. I have updated this to explicitly install the latest 5.1 version, one that I have confirmed to workI believe this fixes #107