what stackpulse tracks
SvelteKit releases from GitHub
StackPulse watches SvelteKit release notes and keeps the original source link close to every summary.
Web development, streamlined StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches SvelteKit release notes and keeps the original source link close to every summary.
upgrade risk
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Migration steps and recommended actions are only shown when the upstream release notes support them.
This release adds clickable links to remote function invocations in development server logs. It also fixes issues involving data requests, navigation hydration, remote functions, asset discovery, and development-time module reloads.
SvelteKit developers may see improved development logs and more reliable behavior for data requests, navigation, remote functions, and asset handling.
This patch fixes image imports used in scripts when either `width` or `height` is missing. The missing dimension is now computed at runtime instead of being output as `NaN`.
Users importing images in scripts with a missing width or height are affected.
Upgrade to version 1.0.1 if your script-imported images are affected by a missing dimension being output as `NaN`.
This patch release fixes Node.js runtime version detection so the adapter accepts all Node.js versions from 26, including odd-numbered versions. It also fixes serving prerendered pages when `paths.base` is configured and updates the `@sveltejs/kit` dependency to 3.2.0.
SvelteKit applications using the Vercel adapter are affected, particularly those targeting Node.js 26 or later or serving prerendered pages with `paths.base` set.
Upgrade to adapter-vercel 7.0.3 to receive these fixes.
This patch release fixes handling of `Range` headers on `HEAD` requests for static assets and prevents unexpected request failures from crashing the server. It also adds support for the `ORIGIN` environment variable when `paths.origin` is not set, and updates the `@sveltejs/kit` dependency to 3.2.0.
SvelteKit adapter-node users are affected, particularly those serving static assets or relying on `ORIGIN` for origin configuration.
This patch improves Bun adapter handling of static assets: client and prerendered files are served regardless of how request paths are percent-encoded, and filenames may include `*` or a leading `:`. It also allows Bun to serve immutable files without invoking JavaScript and adds support for the `ORIGIN` environment variable when `paths.origin` is unset; the release updates `@sveltejs/kit` to 3.2.0.
SvelteKit applications using `@sveltejs/adapter-bun` are affected, particularly those serving encoded static asset paths or relying on the `ORIGIN` environment variable.
Upgrade to `@sveltejs/adapter-bun@1.0.1` to receive the static-file handling fixes and `ORIGIN` support.
This patch prevents the server from crashing when a `text/event-stream` response has immutable headers. It also updates the dependency on `@sveltejs/kit` to version 2.70.4.
SvelteKit applications using the Node adapter may benefit when serving `text/event-stream` responses with immutable headers.
This patch expands Vercel adapter support for Node.js runtimes, including Node.js 26 and future versions, and fixes acceptance of odd-numbered versions starting with Node.js 27. It also escapes prerendered paths in Vercel route patterns and updates the `@sveltejs/kit` dependency to 2.70.4.
SvelteKit projects using the Vercel adapter can target a wider range of Node.js runtimes and receive corrected route patterns for prerendered paths.
This patch release fixes escaping for prerendered paths used in Vercel route patterns. It also updates the dependency on @sveltejs/kit to version 2.70.4.
Users of @sveltejs/adapter-static deploying to Vercel may benefit when prerendered paths are used in route patterns.
Upgrade to version 3.0.11 to receive the Vercel route-pattern escaping fix and dependency update.
This patch release fixes malformed-path handling in `reroute` and escapes cache-control headers in prerendered HTML. It also addresses path traversal on Windows, cross-origin code loading from `//` paths, and redirect following in server-side self-fetch fallbacks.
SvelteKit applications using prerender previews, server-side route resolution, or self-fetch fallbacks may be affected by these fixes, alongside applications that reroute malformed paths or serve prerendered HTML.
Upgrade to @sveltejs/kit@2.70.4 to receive these fixes.
This patch prevents prerendered paths from creating unintended rules in the generated `_redirects` and `_routes.json` files. It also updates the `@sveltejs/kit` dependency to 2.70.4.
Cloudflare adapter users with prerendered paths are affected by the fix to generated routing and redirect rules.
Update to version 7.2.10 to avoid unintended rules for prerendered paths.
This patch updates the `chokidar` dependency to v6. It also fixes packaging to exit after completion when preprocessors leave resources running.
Users of `@sveltejs/package` may benefit from the dependency update and the fix to packaging processes that otherwise remain running after completion.
This patch release fixes several correctness and development-server issues, including restoring function snapshots after reloads with SSR disabled and reusing the original `fetch` across development reloads. It also hardens routing and module boundaries, including preventing server-side route resolution from loading code from another origin and blocking server-only modules from entering browser code via `src/params.js`.
SvelteKit users may benefit from improved routing safety, module isolation, reload behavior, and performance when processing remote form submissions.
Upgrade to @sveltejs/kit 3.1.1 to receive these fixes.
This patch release fixes escaping of prerendered paths in Vercel route patterns. It also adds support for Node.js 26 and future even-numbered Node.js versions, and updates the @sveltejs/kit dependency to 3.1.1.
SvelteKit projects using the Vercel adapter may benefit from corrected route patterns and can target Node.js 26 or future even-numbered Node.js versions.
This patch fixes escaping of prerendered paths used in Vercel route patterns. It also updates the dependency on @sveltejs/kit to version 3.1.1.
Users deploying prerendered paths through Vercel route patterns are affected by the escaping fix.
This patch prevents the server from crashing when a `text/event-stream` response has immutable headers. It also updates the `@sveltejs/kit` dependency to version 3.1.1.
Users of the Node adapter handling `text/event-stream` responses with immutable headers are affected by the crash fix.
Upgrade to @sveltejs/adapter-node@6.0.1 to receive the server crash fix and updated SvelteKit dependency.
This patch release fixes an issue where component types were emitted based on the oldest Svelte version allowed by the dependency range, rather than the installed version.
Developers using SvelteKit with specific Svelte version requirements may be affected by incorrect type emissions.
Update to version 3.0.1 to ensure correct type emissions based on the installed Svelte version.
This release introduces support for CSP hash-reporting keywords and adds a `sveltekit.endpoint` span for server tracing. It also includes several bug fixes related to module handling, deployment recovery, MIME type inference, and focus management.
Developers using CSP hash-reporting keywords or server tracing will benefit from the new features.
This release includes a patch fix related to the detection of the Bun runtime version.
Users relying on the Bun runtime detection in SvelteKit's Vercel adapter may be affected.
Update to this version to ensure accurate Bun runtime detection.
This release includes several fixes for the Cloudflare adapter, addressing issues with dev server startup on certain runtimes, platform proxy management, and tracing functionality.
Users of the Cloudflare adapter in environments like Deno or those utilizing concurrent Vite servers and tracing features are affected.
Update to version 8.0.1 to benefit from the fixes.
This patch release fixes an issue where relative imports in generated types did not work correctly with `nodenext` module resolution.
Users relying on `nodenext` module resolution with relative imports in generated types are affected.
Update to version 3.0.1 if you encounter issues with relative imports in generated types when using `nodenext` module resolution.