chore(deps): upgrade TypeScript to 7#52
Merged
Merged
Conversation
This was referenced Jul 10, 2026
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.
What
Upgrade TypeScript from 5.9.3 to 7.0.2 and regenerate the npm lockfile on top of the repaired frontend dependency baseline from #51.
Why
The standalone Dependabot PR #45 was built on a malformed lockfile and failed every install-dependent gate. Recreating the update from the green #51 baseline isolates the real major upgrade.
Testing
Risks
Moderate dependency-major risk, contained to the compiler/tooling layer. No runtime source changes.
Lockfile rationale
package-lock.json was regenerated normally with Node 22 and npm 10 after selecting TypeScript 7.0.2.
Screenshots
Not applicable; no UI changes.