The old 2.20.x range carried high-severity npm audit advisories (CSRF, dev-mode 404 XSS, handle-hook DoS), which pushed users toward npm audit fix --force — a command that downgrades kit to a 2021 pre-release and breaks the install (issue #38). Bumping within the major plus the safe audit fixes leaves only 3 low-severity transitives, all requiring major downgrades. Recovery steps for affected users are in the changelog.
1.5 KiB
1.5 KiB
2026-08-31 — Calliope 1.3.1 (patch)
Dependency hygiene fix prompted by #38.
What changed
@sveltejs/kitbumped2.20.x→^2.70.3. The older range was flagged bynpm auditwith several high-severity advisories (CSRF protection, dev-mode 404 XSS, handle-hook DoS, unescaped error messages), which pushed users towardnpm audit fix --force— a command that downgrades kit to a 2021 pre-release (0.0.30) and wrecks the install (missing adapter,svelte.config.jsload failure).- Safe non-breaking audit fixes applied (
brace-expansion,js-yaml,nanoid,postcsstransitives). Remaining findings are 3 low-severity transitives only resolvable via SemVer-major downgrades — do not runnpm audit fix --force. - Version bumped to 1.3.1 (web + backend). No feature changes.
For anyone who hit the broken-install state (#38)
Your repo files are fine — the committed package.json / package-lock.json / tsconfig.json are correct, and .svelte-kit/ is generated output that appears after the first sync. Recover with:
cd calliope-web
git checkout -- package.json package-lock.json
Remove-Item -Recurse -Force node_modules
npm ci
npm run dev
The Cannot find base config file "./.svelte-kit/tsconfig.json" line alone is a harmless first-run warning; the real error was config.kit.adapter should be an object with an "adapt" method, caused by --force downgrading SvelteKit.