Update TypeScript to TS 5.0.2 in all projects, vendored files #3721
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
jakebailey
changed the title
|
Now updated to TS 5.0. |
|
Thanks! |
aeschli
approved these changes
Mar 17, 2023
|
Approval bot seems to be stuck? |
hediet
approved these changes
Mar 17, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I'm working on making TS dynamically included. I noticed that
npm run import-typescriptwasn't run after TS was bumped to TS 4.7 which is making that change a little noisy because my change cleans up a bit of the vendored code (which I then can't commit because what's in main is the wrong files already).I could send a PR that just finishes updating the vendored copy to what's defined in
package.json, but it seems easiest to also just jump to the latest version of TypeScript at the same time.This effectively supercedes #3350.