what stackpulse tracks
SvelteKit releases from GitHub
StackPulse watches SvelteKit release notes and keeps the original source link close to every summary.
#stacks/
loading releases…
releases
breaking
security
deprecated
migrations
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 includes several bug fixes addressing issues with route type generation, focus management, and form instance handling.
Developers using SvelteKit may encounter fixed issues related to route types, focus management, and form instance handling.
Update to this version to benefit from the bug fixes.
This release fixes bundling of Svelte libraries listed in `dependencies` and updates dependencies to align with the latest SvelteKit changes.
Users relying on Svelte libraries in `dependencies` will see improved bundling behavior.
Update to this version to ensure proper bundling of Svelte libraries.
This release fixes bundling behavior for Svelte libraries listed in dependencies, ensuring they are bundled instead of externalized. It also includes updates to dependencies.
Users of @sveltejs/adapter-bun who rely on external Svelte libraries in dependencies may need to update their configuration.
Update to @sveltejs/adapter-bun@1.0.0-next.5 if you encounter issues with bundled Svelte libraries.
This release includes fixes for SVG element focus blurring during navigation and making cookie options optional.
Developers using SVG elements or cookie options in SvelteKit may be affected by these fixes.
Update to this version to benefit from the fixes.
This release fixes bundling of dev dependencies and updates dependencies to @sveltejs/kit@3.0.0-next.29.
Users of @sveltejs/adapter-node may need to update due to dependency changes.
Update to @sveltejs/adapter-node@6.0.0-next.14 if using affected features.
This release fixes bundling of dev dependencies and updates dependencies to align with SvelteKit 3.0.0-next.29.
Developers using @sveltejs/adapter-bun may need to update their dependencies to ensure compatibility with SvelteKit 3.0.0-next.29.
Update dependencies to @sveltejs/kit@3.0.0-next.29.
This release introduces a breaking change by rejecting query parameters starting with `x-sveltekit-`. It also includes numerous bug fixes and improvements across various aspects of SvelteKit, such as server-side route resolution, prerendering, and form handling.
Developers using query parameters starting with `x-sveltekit-` will need to update their code to avoid rejection.
Review and update any code that uses query parameters starting with `x-sveltekit-`.
This release introduces significant changes to how static assets are handled, including build-time recording of assets and stricter request method enforcement. It also replaces the `sirv` middleware with a new static asset serving mechanism.
Users relying on dynamically added static assets or non-GET/HEAD requests for static files will need to adjust their workflows.
Review and update any workflows that depend on dynamically adding static assets or non-GET/HEAD requests for static files.
This release introduces a breaking change for static file handling in the Netlify adapter, shifting from `netlify.toml` to the `publish` option. It also adds support for combining `split` and `edge` options.
Projects using `@sveltejs/adapter-netlify` with custom `netlify.toml` configurations for static files will need to update their setup.
Review and update your Netlify adapter configuration to use the `publish` option for static files.
This release introduces a breaking change by switching the server build process from Bun.build to Vite, affecting how production dependencies are handled and limiting `buildOptions` to executables.
Users of @sveltejs/adapter-bun need to update their build configurations due to the switch from Bun.build to Vite for server builds.
Review and update build configurations to align with the new Vite-based server build process.
This release includes a minor internal change to how the Svelte configuration is read, utilizing `@sveltejs/load-config`.
Developers using SvelteKit may notice internal changes in configuration handling.
This release introduces several breaking changes, including the removal of the `Server` constructor and `SSRManifest` from public types, and replaces `builder.generateManifest` with `builder.generateServerInstance` and `builder.manifest`. It also adds new features for adapters and fixes various bugs.
Developers using the `Server` constructor, `SSRManifest`, or `builder.generateManifest` will need to update their code.
Review the breaking changes and update your code accordingly.
This release introduces breaking changes to the adapter instrumentation API and builder manifest generation, along with fixes for ISR functions and file tracing.
Developers using the Vercel adapter and relying on the previous instrumentation API or manifest generation will be affected.
Review the breaking changes and update your code accordingly.
This release introduces breaking changes to the adapter-node instrumentation API and replaces `builder.generateManifest` with `builder.generateServerInstance` and `builder.manifest`. It also includes various dependency updates.
Developers using `@sveltejs/adapter-node` and relying on the `builder.generateManifest` API or the instrumentation API will be affected.
Update your code to use the new `builder.generateServerInstance` and `builder.manifest` APIs and ensure environment variables are populated correctly.
This release introduces breaking changes to the Netlify adapter for SvelteKit, including updates to the instrumentation API and manifest generation. It also includes several fixes and improvements, such as better handling of serverless functions and route requests.
Users of the Netlify adapter for SvelteKit will need to update their code to accommodate the breaking changes in the instrumentation API and manifest generation.
Review the breaking changes and update your code accordingly before upgrading to this version.
This release introduces a new `applyReroute` helper for serverless adapters and includes several fixes and improvements to response handling, logging, and invalidation behavior.
Developers using SvelteKit adapters for split serverless function deployments and those relying on response logging or invalidation behavior may be affected.
Update to this version if you need the new `applyReroute` helper or are experiencing issues with response logging or invalidation behavior.
This release fixes issues with ISR data endpoints for server-only routes and correctly applies reroute results for apps with split serverless functions. It also updates dependencies to @sveltejs/kit@3.0.0-next.25.
Users of @sveltejs/adapter-vercel with server-only routes or split serverless functions may need to update due to fixes in ISR data endpoints and reroute handling.
Update to @sveltejs/adapter-vercel@7.0.0-next.8 if you use server-only routes or split serverless functions to benefit from the fixes.
This release focuses on fixing the `reroute` functionality for apps using split serverless functions and updates dependencies.
Users deploying SvelteKit apps with split serverless functions on Netlify are affected.
Update to this version to ensure `reroute` works correctly with split serverless functions.
This release introduces support for the `QUERY` HTTP method and enhances font preloading with filename context. It also includes numerous fixes for form actions, error handling, and performance improvements.
Developers using SvelteKit's form actions, error handling, or HTTP methods may need to review changes.
Review the changes and update your code if you use affected features like form actions or HTTP methods.
This release primarily focuses on bug fixes and dependency updates, with a notable fix for handling `EEXIST` errors during symlinking.
Users experiencing issues with symlinking traced files may benefit from this release.