77ab341)breaking: platform.context is now the modern Netlify Functions ([#15203](https://github.com/sveltejs/kit/pull/15203))
context
Previously, this was the AWS Lambda-style context.
If you were using this in your app (unlikely), you will need to update your code to read from new fields.
feat: Migrate to the modern Netlify Functions API (#15203)
The Netlify adapter now generates "v2" Netlify Functions, which uses modern standards (ESM, Request, Response) instead of the legacy "Lambda-compatible" or "v1" format. Under the hood, this greatly simplifies the adapter code and improves maintainability.
For more details on features this unlocks for your SvelteKit app, see https://developers.netlify.com/guides/migrating-to-the-modern-netlify-functions/.
feat: allow configuring redirects in netlify.toml (#15203)
The limitation of only being able to configure redirects via the _redirects file has been removed.
import.meta.DEV with import.meta.env.DEV in generated code (#15285)feat: add scroll property to NavigationTarget in navigation callbacks (#15248)
Navigation callbacks (beforeNavigate, onNavigate, and afterNavigate) now include scroll position information via the scroll property on from and to targets:
from.scroll: The scroll position at the moment navigation was triggeredto.scroll: In beforeNavigate and onNavigate, this is populated for popstate navigations (back/forward) with the scroll position that will be restored, and null for other navigation types. In afterNavigate, this is always the final scroll position after navigation completed.This enables use cases like animating transitions based on the target scroll position when using browser back/forward navigation.
feat: hydratable's injected script now works with CSP (#15048)
fix: put preloads before styles (#15232)
fix: suppress false-positive inner content warning when children prop is forwarded to a child component (#15269)
fix: fetch not working when URL is same host but different than paths.base (#15291)
fix: navigate to hash link when base element is present (#15236)
fix: avoid triggering handleError when redirecting in a remote function (#15222)
fix: include test directory in generated tsconfig.json alongside existing tests entry (#15254)
fix: generate tsconfig.json using the value of kit.files.src (#15253)
fix: ensure inlined CSS follows paths.assets and paths.relative settings (#15153)
fix: emit script CSP nonces when unsafe-inline is present if strict-dynamic is also present (#15221)
fix: re-export browser/dev from esm-env (#15206)
fix: use validated args in batch resolver in both csr and ssr (#15215)
fix: ensure CSS inlining includes components that are conditionally rendered (#15153)
fix: only match rest params with matchers when the matcher matches (#15216)
fix: properly handle percent-encoded anchors (e.g. <a href="#sparkles-%E2%9C%A8">) during prerendering. (#15231)
Picture type from vite-imagetools (#15225)buttonProps from experimental remote form functions; use e.g. <button {...myForm.fields.action.as('submit', 'register')}>Register</button> button instead (#15144)