chore: hold TypeScript at 5 until the toolchain can take 7 - #26
Merged
Conversation
TypeScript 7 was attempted and cannot be installed here. The blocker is upstream, not in this repo: @sveltejs/kit declares a peer range of ^5.3.3 || ^6.0.0, and svelte-check crashes on startup against the 7.x compiler API before it checks a single file. Forcing it past the peer conflict would leave the project with no working type check, which is a worse position than staying on 5 — so this records the constraint instead of leaving a red pull request to be reopened and rediscovered every time a 7.x patch ships. The entry is written to be removed: once SvelteKit widens that range the bump comes back as its own PR and gets judged like any other major. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
I attempted TypeScript 7 and it cannot be installed here. The blocker is upstream, not anything this repo can fix:
@sveltejs/kit@2.70.1declarestypescript: '^5.3.3 || ^6.0.0'— 7 is explicitly outside its supported peer range, so npm refuses the tree.svelte-checkcrashes on startup against the 7.x compiler API —TypeError: Cannot read properties of undefined (reading 'useCaseSensitiveFileNames')— before it checks a single file. The current 4.7.3 still declares onlytypescript: '>=5.0.0'and fails the same way.Forcing past the peer conflict would leave the project with no working type check at all, which is a worse position than staying on 5. So rather than leave #19 open and red — reopened and rediscovered every time a 7.x patch ships — this records the constraint next to the two majors already held for the same kind of reason.
The entry is written to be removed: once SvelteKit widens that range, the bump returns as its own PR and gets judged like any other major.
🤖 Generated with Claude Code