Node 26 entered Active LTS on 2026-10-28 and Node 24 went to maintenance on 2026-10-20, so the toolchain moves with them: .nvmrc, engines and @types/node all say 26. TypeScript 7.0 is GA but still has no programmatic API, and svelte-check peers `typescript ^5 || ^6`. So this uses Microsoft's documented side-by-side aliases instead of choosing one: "@typescript/native": "npm:typescript@~7.0.2" -> tsc (7.0.2) "typescript": "npm:@typescript/typescript6@~6.0.2" -> the 6.0.3 API `npm run check` therefore type-checks .svelte files with TS 6 (svelte-check) and every .ts file with both. `tsc --version` is 7.0.2; `tsc6` is 6.0.3. tsconfig targets ES2025 with lib ES2025, which is only honest if the oldest Chrome allowed to install has every ES2025 built-in. That is Chrome 136 (RegExp.escape), so minimum_chrome_version goes 120 -> 136 and Vite's build.target follows the same CHROME_FLOOR constant. manifest.test.ts pins all three so they cannot drift apart. Users below 136 keep what they have installed; they just stop receiving updates. Built output: the manifest changes only minimum_chrome_version, the JS chunks are byte-identical apart from a CSS hash, and the CSS loses one -webkit-user-select prefix Chrome 136 no longer needs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2 lines
3 B
Plaintext
2 lines
3 B
Plaintext
26
|