Commit activity
Last 12 weeks · 104 commits
Community health
4 of 6 standards met
Recent PRs & issues
Closes # Description Adds a devtools addons https://github.com/baseballyama/vite-devtools-svelte Do not merge at this point. Offsite. Checklist Update snapshots (if applicable) Add a changeset (if applicable) Allow maintainers to edit this PR I care about what I'm doing, no matter the tool I use (Notepad, Sublime, VSCode, AI...)
Updates dependencies and GitHub Actions. Keeps TypeScript 6 for now because SvelteKit, svelte-check, and typescript-eslint do not yet support TypeScript 7; the updater remains unpinned so future runs retry it. Includes minor verkit, tsdown, and Vitest compatibility fixes plus patched transitive resolutions. Changesets included.
Recent fixes
Summary retains explicit Kit 2 generated declaration entries in a custom include array. After a successful Kit 3 installation and sync, the retained still augments with the old route inventory and old matcher imports. Valid consumers of a newly added typed route fail, and the migrated original string matcher accepts a numeric parameter without a diagnostic. Steps to reproduce This reduced case was executed through the released migration and the checks below. It retains the custom include array from a supplied larger Kit 2 migration case and removes unrelated application, browser, lint and formatting inputs. Use Node.js 22.23.2 and npm 12.0.2 in an empty disposable directory. 1. Save the following as , run , then remove . 2. Run the Kit 2 baseline check, then apply all released migration tasks. Keep so this is an ordinary in-place migration with generated Kit 2 declarations present. 3. Pin the migrated dependency graph to the exact checked versions below. Run this with via standard input, then run and . Removing only the dependency tree and lock avoids an old installed graph during this probe; leave intact. Both install and check pass at this point. The emitted contains CORS and adapter-node origin tasks, neither of which affects this checker-only case, and contains no task about obsolete generated declaration includes. 4. Add a new Kit 3 numeric matcher, route and typed consumer by running this with via standard input, then run again. Expected behavior The migrated TypeScript project should use Kit 3's generated route inventory and matcher output types through and , while preserving real source, test and root config coverage. and its call should pass after sync. The original migrated matcher returns a string, so supplying a number for its should fail. The Kit 3 migration guide specifies the new base and consolidated parsed-value matchers. The released CLI tsconfig task supports an existing custom include array. This issue concerns a supported custom array that explicitly includes generated Kit 2 declarations, rather than a claim that every default migration fails. Actual behavior The Kit 2 baseline check exits 0 with zero errors and warnings. Migration reports , changes to , preserves all three include entries, and removes the original per-file matcher in favor of . A fresh Kit 3 install succeeds, and the migrated original app still checks with zero errors and warnings before adding the new route. After adding the new route, exits 1 with three errors and zero warnings in . The meaningful diagnostics are: The last diagnostic is an excerpt from the longer route overload union. The new already contains . The old has byte-identical SHA256 before and after Kit 3 sync and still declares , and imports , which migration removed. Removing only the three obsolete generated declaration entries from , while retaining , , , , and , makes the same valid consumer pass with zero errors and warnings. Keeping the stale declaration in the project and checking only for the original route passes incorrectly; with the corrected includes it exits 1 with . Runtime or environment Executed with sv 1.1.0, Node.js 22.23.2 and npm 12.0.2. Kit 2 baseline: 2.70.3, Svelte 5.57.1, TypeScript 5.9.3, Vite 6.4.3, Vite Svelte plugin 5.1.1 and adapter-node 5.5.7. Kit 3 graph: Kit 3.0.0, Svelte 5.57.1, TypeScript 6.0.3, Vite 8.0.12, Vite Svelte plugin 7.3.1 and adapter-node 6.0.0. Both use svelte-check 4.7.6 and 22.19.15. The Kit 3 readback has no invalid or missing dependencies. No force or legacy peer flags were used. Evidence Expected source: Kit 3 migration guide at stable revision 090496890cedbbff15d998695d48cd31e7d698b7 specifies the migration; its Params section specifies parsed-value matchers. Kit 3's declarations define from the generated route inventory, and resolve uses that inventory. The sv 1.1.0 tsconfig task supports existing custom includes while retargeting the generated config. Failure source: Executed inline fixture and commands above. The migrated include array retains , the file survives sync unchanged, the valid new consumer fails with the quoted diagnostics, and changing only obsolete generated includes restores the same check. Evidence provenance: observed Local verification: reproduced Reproduction completeness: complete The primary violation evidence is the complete reduced released-tool replay above. A supplied larger migration case motivated the probe and is not required to reproduce it. The baseline, failure, correction and discriminating controls above were executed. The released task currently preserves through at tsconfig.ts lines 80-85. This is a code locator for the observed output, not a prescribed implementation. Restoration check Replay the same Kit 2 input with its generated declarations present through the released migration, install a valid Kit 3 graph, and add the numeric route and consumer above. The valid new and consumers must pass using the current inventory after sync. The old string matcher must still reject , and the new numeric matcher must reject a string . The resulting project must continue to check real test and root config inputs. In the observed correction, changing in , and independently in , to a string produced the intended string-to-number error in each file with exit 1. A green check caused by dropping test/config coverage or weakening route types does not restore this contract.
Repository: sveltejs/cli. Description: The Svelte CLI Stars: 513, Forks: 110. Primary language: TypeScript. Languages: TypeScript (90.5%), JavaScript (4.5%), Svelte (4.2%), Shell (0.4%), HTML (0.2%). License: MIT. Homepage: https://svelte.dev/docs/cli Topics: cli, sv, svelte, svelte-migrate. Latest release: sv@1.4.0 (1d ago). Open PRs: 10, open issues: 18. Last activity: 38m ago. Community health: 75%. Top contributors: jycouet, manuel3108, github-actions[bot], sacrosanctic, AdrianGonz97, benmccann, Rich-Harris, dummdidumm, teemingc, hyunbinseo and others.