chore(deps): bump vite 6→8 + @sveltejs/vite-plugin-svelte 5→7#179
Merged
Conversation
Combined major upgrade — the two are peer-coupled and cannot be bumped independently: - @sveltejs/vite-plugin-svelte@7.2.0 requires vite ^8.0.0 - @sveltejs/vite-plugin-svelte@5.x requires vite ^6.0.0 So bumping only one causes an npm ERESOLVE. This commit does both together. Regenerated package-lock.json cleanly (the old lock pinned @sveltejs/vite-plugin-svelte-inspector@4.0.1 which peers plugin-svelte ^5). Verified locally: - svelte-check: 0 errors (36 pre-existing a11y warnings) - vitest: 61/61 pass - npm run build: ✓ built in 3.40s (vite 8 now uses rolldown) Closes #168 (vite 6→8) and #170 (vite-plugin-svelte 5→7).
This was referenced Jul 20, 2026
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
| }, | ||
| "devDependencies": { | ||
| "@sveltejs/vite-plugin-svelte": "^5", | ||
| "@sveltejs/vite-plugin-svelte": "^7", |
🔍 Cora AI Code Review❌ Blocked — critical issues found. 🔴 Error (1)
Review powered by cora-cli · BYOK · MIT |
Merged
ajianaz
added a commit
that referenced
this pull request
Jul 20, 2026
Patch release — Windows Documents-tab fix, uteke 0.8.x compatibility, and a full dependency sweep (incl. vite 6→8). - bump version 0.3.1 → 0.3.2 (package.json, Cargo.toml, Cargo.lock, tauri.conf.json) - CHANGELOG entry Contents (since v0.3.1): - Fixed: Windows "uteke CLI not found" — HTTP-first version gate reads /health `version`; CLI discovery now PATHEXT-aware (#171, #180) - Fixed: uteke 0.8.x room-document compat — /room/summary-document with legacy /room/document fallback (#178) - Changed: version gate HTTP-first for local servers too (#180) - Deps: vite 6→8 + @sveltejs/vite-plugin-svelte 5→7 (#179), tokio 1.52→1.53 (#175), serde/thiserror/toml/tauri-plugin-dialog, @codemirror/language/dompurify/marked, actions/setup-node 6→7 (#172)
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
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.
Combined major upgrade.
vite-plugin-svelte@7peersvite@^8;vite-plugin-svelte@5peersvite@^6— so #168 and #170 each fail npm ERESOLVE on their own. This PR bumps both together and regeneratespackage-lock.json.Verified locally: svelte-check 0 errors, vitest 61/61,
npm run build✓ (3.40s, vite 8 = rolldown).Closes #168, #170.