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 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 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.