feat: update @sveltejs/kit to 2.60.1 #minor

[public-glueops-renovatebot]

This PR contains the following updates:

Package	Change	Age	Confidence
@sveltejs/kit (source)	2.50.1 → 2.60.1

---

CPU exhaustion in SvelteKit remote form deserialization (experimental only)

GHSA-88qp-p4qg-rqm6

More information

Details

Versions of @sveltejs/kit prior to 2.52.2 with remote functions enabled are vulnerable to CPU exhaustion. Malformed form data can cause the server to become unresponsive while processing a request, resulting in denial of service.

Only applications using both experimental.remoteFunctions and form are vulnerable.

Severity

• CVSS Score: 6.9 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

References

• https://github.com/sveltejs/kit/security/advisories/GHSA-88qp-p4qg-rqm6
• https://github.com/sveltejs/kit/commit/3e607b314aec9e5f278d32847945b8b6323e1cb8
• https://github.com/sveltejs/kit/releases/tag/@​sveltejs/kit@2.52.2
• https://github.com/advisories/GHSA-88qp-p4qg-rqm6

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

@​sveltejs/kit: query.batch cross-talk

GHSA-hgv7-v322-mmgr

More information

Details

query.batch() could, under very rare and specific timings, cause concurrent requests from different users to merge and resolve under single request context, enabling cross-user data disclosure.

Severity

• CVSS Score: 5.9 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

References

• https://github.com/sveltejs/kit/security/advisories/GHSA-hgv7-v322-mmgr
• https://github.com/advisories/GHSA-hgv7-v322-mmgr

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

sveltejs/kit (@​sveltejs/kit)

v2.60.1

Compare Source

Patch Changes

• chore: bump svelte and devalue (#​15836)

• fix: prevent query.batch cross-talk (dadaefc)

v2.60.0

Compare Source

Minor Changes

• feat: allow 'submit' and 'hidden' form fields to accept numbers and booleans (#​15802)

• feat: warn on unread form remote function validation issues (#​15653)

Patch Changes

• fix: abort navigation after async rendering if obsolete (#​15811)

• fix: skip refreshing queries on full-page reload form submissions (#​15803)

v2.59.1

Compare Source

Patch Changes

• fix: resolve paths to route files with the letter drive on Windows (#​15793)

v2.59.0

Compare Source

Minor Changes

• feat: support query.batch in requested(...) (#​15751)

• breaking: on the server, make the promise returned from refresh represent adding the refresh to the map, not the time it takes to run the remote function (#​15705)

• feat: experimental query.live function (#​15705)

Patch Changes

• fix: unwrap Promise in RemoteCommand output type (#​15771)

• fix: empty call to .updates() on a command/form invocation means "don't update anything" (#​15705)

• fix: form.fields.foo.as('checkbox', default_value) now works (#​15752)

• fix: remote forms with default values defined by field.as('text', defaultValue) now correctly reset to the provided default values once submitted (#​15753)

• fix: make sure queries always get started correctly (#​15705)

• fix: allow plain functions as overrides in updates (#​15705)

v2.58.0

Compare Source

Minor Changes

• breaking: require limit in requested (as originally intended) (#​15739)

• feat: RemoteQueryFunction gains an optional third generic parameter Validated (defaulting to Input) that represents the argument type after schema validation/transformation (#​15739)

• breaking: requested now yields { arg, query } entries instead of the validated argument (#​15739)

Patch Changes

• fix: allow query().current, .error, .loading, and .ready to work in non-reactive contexts (#​15699)

• fix: prevent deep_set crash on nullish nested values (#​15600)

• fix: restore correct RemoteFormFields typing for nullable array fields (e.g. when a schema uses .default([])), so .as('checkbox') and friends work again (#​15723)

• fix: don't warn about removed SSI comments in transformPageChunk (#​15695)

  Server-side include (SSI) directives like <!--#include virtual="..." --> are HTML comments that are replaced by servers such as nginx. Previously, removing them in transformPageChunk would trigger a false positive warning about breaking Svelte's hydration. Since SSI comments always start with <!--# and Svelte's hydration comments never do, they can be safely excluded from the check.

• Change enhance function return type from void to MaybePromise. (#​15710)

• fix: throw an error when resolve is called with an external URL (#​15733)

• fix: avoid FOUC for CSR-only pages by loading styles and fonts before CSR starts (#​15718)

• fix: reset form result on redirect (#​15724)

v2.57.1

Compare Source

Patch Changes

• fix: better validation for redirect inputs (10d7b44)

• fix: enforce BODY_SIZE_LIMIT on chunked requests (3202ed6)

• fix: use default values as fallbacks (#​15680)

• fix: relax form typings for union types (#​15687)

v2.57.0

Compare Source

Minor Changes

• feat: return boolean from submit to indicate submission validity for enhanced form remote functions (#​15530)

Patch Changes

• fix: use array type for select fields that accept multiple values (#​15591)

• fix: silently 404 Chrome DevTools workspaces request in dev and preview (#​15656)

• fix: config.kit.csp.directives['trusted-types'] requires 'svelte-trusted-html' (and 'sveltekit-trusted-url' when a service worker is automatically registered) if it is configured (#​15323)

• fix: avoid inlineDynamicImports ignored with codeSplitting warning when using Vite 8 (#​15647)

• fix: reimplement treeshaking non-dynamic prerendered remote functions (#​15447)

v2.56.1

Compare Source

Patch Changes

• chore: update JSDoc (#​15640)

v2.56.0

Compare Source

Minor Changes

• breaking: rework client-driven refreshes (#​15562)

• breaking: stabilize remote function caching by sorting object keys (#​15570)

• breaking: add run() method to queries, disallow awaiting queries outside render (#​15533)

• feat: support TypeScript 6.0 (#​15595)

• breaking: isolate command-triggered query refresh failures per-query (#​15562)

• feat: use hydratable for remote function transport (#​15533)

• feat: allow form fields to specify a default value (field.as(type, value)) (#​15577)

Patch Changes

• fix: don't request new data when .refresh is called on a query with no cache entry (#​15533)

• fix: allow using multiple remote functions within one async derived (#​15561)

• fix: avoid false-positive overridden Vite base setting warning when setting a paths.base in svelte.config.js (#​15623)

• fix: manage queries in their own $effect.root (#​15533)

• fix: avoid inlineDynamicImports deprecation warning when building the service worker with Vite 8 (#​15550)

• fix: correctly escape backticks when precomputing CSS (#​15593)

• fix: discard obsolete forks before finishing navigation (#​15634)

• chore: tighten up override implementation (#​15562)

• fix: ensure the default Svelte 5 error.svelte file uses runes mode (#​15609)

• fix: deduplicate same-cache-key batch calls during SSR (#​15533)

• fix: decrement pending_count when form callback doesn't call submit() (#​15520)

v2.55.0

Compare Source

Minor Changes

• feat: page and layout params with matchers are now type narrowed in $app/types, leading to better type safety when working with params in $app/types, $app/state, and hooks. (#​15502)

v2.54.0

Compare Source

Minor Changes

• feat: allow error boundaries to catch errors on the server (#​15308)

Patch Changes

• chore: upgrade devalue (#​15535)

• fix: don't wait for remote functions that are not awaited in the template (#​15280)

• feat: allow resolve() to accept pathnames with a search string and/or hash (#​15458)

• chore: remove deprecation warnings for config.kit.files.* options when validating the Svelte config file (#​15482)

• fix: handles form target attribute in remote form redirects (#​15457)

v2.53.4

Compare Source

Patch Changes

• fix: avoid Vite warning about unknown codeSplitting option (#​15451)

v2.53.3

Compare Source

Patch Changes

• fix: prevent overlapping file metadata in remote functions form (faba869)

v2.53.2

Compare Source

Patch Changes

• fix: server-render nested form value sets (#​15378)

• fix: use deep partial types for form remote functions .value() and .set(...) (#​14837)

• fix: provide correct url info to remote functions (#​15418)

• fix: allow optional types for remote query/command/prerender functions (#​15293)

• fix: allow commands in more places (#​15288)

v2.53.1

Compare Source

Patch Changes

• fix: address warning about inlineDynamicImports when using Vite 8 (#​15403)

v2.53.0

Compare Source

Minor Changes

• feat: support Vite 8 (#​15024)

Patch Changes

• fix: remove event listeners on form attachment cleanup (#​15286)

• fix: apply queries refreshed in a form remote function when a redirect is thrown (#​15362)

v2.52.2

Compare Source

Patch Changes

• fix: validate form file information to prevent amplification attacks (3e607b3)

• chore: upgrade devalue and svelte (#​15339)

• fix: parse file offset table more strictly (f47c01b)

v2.52.0

Compare Source

Minor Changes

• feat: match function to map a path back to a route id and params (#​14997)

Patch Changes

• fix: respect scroll-margin when navigating to a url-supplied anchor (#​15246)

• fix: resolve will narrow types to follow trailing slash page settings (#​15027)

v2.51.0

Compare Source

Minor Changes

• 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 triggered
  • to.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)

Patch Changes

• 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)

v2.50.2

Compare Source

Patch Changes

• 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)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • ""
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

[public-glueops-renovatebot]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.