Fresh-clone npm install fails: typescript ^7.0.2 exceeds @sveltejs/kit peer range (^5.3.3 || ^6.0.0) #81

A fresh clone + npm install hits ERESOLVE:

• package.json pins "typescript": "^7.0.2" (bumped from ^6.0.2 by dependabot in deps(npm): bump the npm-all group with 10 updates #75, commit 8adca515).
• @sveltejs/kit@2.69.2 declares peerDependencies.typescript: "^5.3.3 || ^6.0.0" (optional peer). TS 7 is outside the range, and npm's resolver refuses.

Why CI never sees it: the committed package-lock.json is internally valid, so npm ci succeeds and CI stays green. The failure only exists for npm install from scratch — i.e. exactly the command a new contributor runs first. (#78 switches setup-dev.sh to npm ci, which fixes the symptom for people using the setup script; this issue is the root cause.)

The question

Is TS 7 intentional here?

• If yes (it works in practice and you want to stay ahead of kit's declared range): an overrides entry in package.json would document that decision and let npm install resolve.
• If no: pinning back to ^6 restores a clean resolve, and a dependabot ignore rule for typescript major bumps prevents recurrence until kit widens its range.

Happy to PR either shape once you pick one.