build!: Upgrade to TypeScript 5.0#178
Merged
Merged
Conversation
SimonAlling
added a commit
that referenced
this pull request
Oct 13, 2025
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
While this probably doesn't break any existing userscripts, I consider this a BREAKING change because upgrading to a new TypeScript version means that future changes might accidentally introduce syntax not supported by earlier versions. Also, I'm looking into Semantic Versioning for TypeScript Types, which lists two "recommended support policies for TypeScript compiler versions":
In the absence of a documented support policy, I think it makes sense to default to simple majors.