Never miss a release that matters
AI-powered summaries of every GitHub release.
AI Summaries
Changelogs condensed into clear, actionable insights.
Always Free
Track up to 5 packages at no cost, forever.
Weekly Digest
A curated summary of every release, delivered weekly.
TL;DR
SvelteKit 3.0 introduces significant breaking changes to project structure, including a new #lib alias and stricter server-only directory enforcement.
Breaking
- Replace
$libalias with#liband removefiles.libconfig. - Server-only directories (
/server/) are now treated as server-only globally (excludingsrc/routesand assets). handle'sresolvemust now return aPromise.getRequestandsetResponseare now synchronous.page.urlis now immutable at the type level.invalidateAllis deprecated in favor ofrefreshAll.defineEnvVarsmoved to@sveltejs/kit/env.- Cross-origin form submissions now require a
Content-Typeheader. experimental.handleRenderingErrorsflag removed.- CORS handling for static directory requests is now delegated to Vite during development.
New
- Support for hyphens in parameter and matcher names.
- Added
ErrorPropsto generated types. - Import aliases are now transformed into relative imports in files.
Fixes Worth Knowing
- Fixed CSRF protection to enable in non-production
NODE_ENVbuilds. - Resolved an issue where client-side code was incorrectly bundled by Cloudflare Wrangler.
- Fixed
<svelte:boundary>to properly reset on client navigation.
Before You Upgrade
- Update all
$libimports to#lib. - Update
handlehooks to ensureresolvereturns aPromise. - Migrate
invalidateAllcalls torefreshAll.
TL;DR
Documentation for @sveltejs/enhanced-img has been updated to use the correct library alias.
TL;DR
This update ensures compatibility between adapter-node and SvelteKit 3 prereleases while fixing critical build issues on Windows.
Fixes Worth Knowing
- Resolved an issue where entrypoints (the main files that start the app) were not bundling correctly on Windows.
- Fixed peer dependency conflicts to allow SvelteKit 3 prerelease versions to be used.
TL;DR
SvelteKit has improved environment variable organization and strengthened security for non-production builds.
Breaking
defineEnvVarshas moved to@sveltejs/kit/env(utility for type-safe environment variables).
Fixes Worth Knowing
- CSRF protection is now active in builds where
NODE_ENVis not set to production. - CSS URL references are now correctly absolute when
paths.relativeis disabled. - Improved type generation for destructured
loadandactionsexports. - Updated
MAX_COOKIE_SIZEto comply with RFC 6265bis (standard for HTTP state management).
Before You Upgrade
- Update your imports for
defineEnvVarsto use the new@sveltejs/kit/envpath.
TL;DR
SvelteKit now correctly supports using pre-release versions of SvelteKit 3, ensuring compatibility as you upgrade to the latest features.
Fixes Worth Knowing
The adapters for Cloudflare and Auto now correctly handle peer dependencies when using pre-release versions of SvelteKit 3. This resolves potential installation or runtime issues when working with the latest SvelteKit development builds.
TL;DR
SvelteKit 3.0.0-next.8 is now compatible with pre-release versions of itself, resolving dependency issues when using the latest development builds.
Fixes Worth Knowing
Adapters for Vercel and Netlify have been updated to ensure necessary files are included in published packages, preventing potential deployment errors.
Before You Upgrade
No specific action is needed, but ensure you are using the latest versions of @sveltejs/adapter-vercel and @sveltejs/adapter-netlify alongside SvelteKit 3.0.0-next.8 for optimal compatibility.
TL;DR
SvelteKit now supports pre-release versions of SvelteKit 3, resolving compatibility issues for developers working with the latest SvelteKit features.
Fixes Worth Knowing
SvelteKit now correctly handles peer dependencies when using pre-release versions of SvelteKit 3, preventing potential installation or runtime errors. (Peer dependencies: external packages required by a project)
TL;DR
SvelteKit now correctly disables buffering for server-sent events (streaming data) when using reverse proxies like Nginx, improving real-time application responsiveness.
Fixes Worth Knowing
- Server-sent events now stream without buffering when used with common reverse proxies.
- Socket file management was improved to prevent errors on startup.
TL;DR
Vercel adapter updates prevent incorrectly cached 404 errors for static assets (files like images, CSS) in your SvelteKit applications.
Fixes Worth Knowing
A fix prevents static assets from being incorrectly cached as 404 errors when deployed to Vercel. This ensures your site displays correctly after deployment.
TL;DR
SvelteKit now exports the EnhancedImgAttributes type, improving type safety when working with the <EnhancedImg> component (image optimization).
New
- The
EnhancedImgAttributestype is now exported, allowing for better type checking and autocompletion when configuring the<EnhancedImg>component.
Fixes Worth Knowing
- Fixed an issue where imports containing a question mark (
?) would incorrectly trigger transformations, potentially causing errors.
TL;DR
SvelteKit now avoids conflicts with user-defined environment variables, preventing unexpected behavior when using custom App.Platform properties.
Fixes Worth Knowing
A potential type collision issue with user-defined App.Platform environment properties has been resolved, ensuring your custom environment variables function as expected within your SvelteKit application. (Environment variables: settings for your application)
TL;DR
SvelteKit static site adapters now correctly handle homepage definitions, ensuring links work as expected when deployed.
Breaking
- The
adapter-staticadapter now requires a correctly formatted "homepage" field inpackage.json(project metadata).
Fixes Worth Knowing
- Fixed an issue where links wouldn’t resolve correctly on static sites (websites served as HTML files) due to incorrect homepage configuration.
Before You Upgrade
- Verify your
package.jsonfile includes a valid "homepage" field pointing to your deployed site’s base URL.
TL;DR
SvelteKit now supports AMP (Accelerated Mobile Pages) components, enabling faster loading and improved SEO for mobile content.
New
- Added support for AMP components via
@sveltejs/ampallowing creation of optimized mobile pages.
Fixes Worth Knowing
- No user-facing fixes in this release.
Before You Upgrade
- No specific upgrade steps are needed.
TL;DR
SvelteKit now correctly handles deployments on Windows machines when using the Netlify adapter.
Fixes Worth Knowing
- Fixed an issue preventing successful builds on Windows (operating system).
Before You Upgrade
- No action needed.
TL;DR
SvelteKit projects now use Vite 4 (build tool), which may require updating your project’s dependencies.
Breaking
- Vite 4 Upgrade: (build tool) May require dependency updates.
New
- vitePreprocess: (Vite plugin) Adds support for processing files with Vite.
Fixes Worth Knowing
- Sverdle Accessibility: (example app) Improved accessibility in the Sverdle demo application.
Before You Upgrade
- Review your project’s dependencies and update any incompatible packages after upgrading to Vite 4.