Update vulnerable Svelte build toolchain - #310
Open
PathGao wants to merge 13 commits into
Open
Conversation
added 13 commits
July 31, 2026 11:07
Contributor
Author
|
@alecdotdev This is the next stacked PR after #308. It updates the Svelte build toolchain and makes the full resolved lockfile clean under |
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.
Fixes #309
Updates SvelteKit, Svelte, Vite, and the matching adapter/plugin/check packages within their existing major release lines. The lockfile refresh also updates affected transitive packages.
Pins
cookieto 0.7.2 because the latest SvelteKit 2 dependency range still resolves its vulnerable 0.6.0 release.The complete resolved lockfile is clean under
npm audit.This is the next stacked change after #308; merge the already-listed predecessor PRs first, then this PR.
Validated with
npm ci,npm run check(0 errors; one Settings drag-header accessibility warning detected by the newer checker is being handled separately),npm test(136 passing),npm run build,npm audit(0 vulnerabilities), andcargo test(21 passing).