chore(deps): update dependency svelte to ^5.2.8

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
svelte (source)	^5.1.9 -> ^5.2.8

---

Release Notes

sveltejs/svelte (svelte)

v5.2.8

Compare Source

Patch Changes

• fix: correctly prune each blocks (#​14403)

• fix: provide temporary LegacyComponentType (#​14257)

• fix: attach spread attribute events synchronously (#​14387)

• fix: ensure last empty text node correctly hydrates (#​14425)

• fix: correctly prune key blocks (#​14403)

v5.2.7

Compare Source

Patch Changes

• fix: always use set for private identifiers (#​14378)

v5.2.6

Compare Source

Patch Changes

• fix: remove template expression inlining (#​14374)

v5.2.5

Compare Source

Patch Changes

• fix: correctly handle srcObject attribute on video elements (#​14369)

• add contentvisibilityautostatechange event to element definitions (#​14373)

• fix: tighten up export default validation (#​14368)

• fix: include method definitions in class private fields (#​14365)

v5.2.4

Compare Source

Patch Changes

• fix: ensure internal cloning can work circular values (#​14347)

• fix: correctly update dynamic member expressions (#​14359)

• fix: ensure is_pure takes into account $effect.tracking() (#​14333)

• fix: coerce value to number when hydrating range/number input with changed value (#​14349)

v5.2.3

Compare Source

Patch Changes

• fix: ensure dynamic call expressions correctly generate output (#​14345)

v5.2.2

Compare Source

Patch Changes

• fix: treat property accesses of literals as pure (#​14325)

v5.2.1

Compare Source

Patch Changes

• fix: mark pseudo classes nested inside :not as used (#​14303)

• fix: disallow invalid attributes for <svelte:window> and <svelte:document> (#​14228)

• fix: ensure props passed to components via mount are updateable (#​14210)

• fix: mark subtree dynamic for img with loading attribute (#​14317)

• fix: avoid relying on Node specifics within compiler (#​14314)

v5.2.0

Compare Source

Minor Changes

• feat: better inlining of static attributes (#​14269)

v5.1.17

Compare Source

Patch Changes

• fix: account for :has(...) as part of :root (#​14229)

• fix: prevent nested pseudo class from being marked as unused (#​14229)

• fix: use strict equality for key block comparisons in runes mode (#​14285)

• fix: bump is-reference dependency to fix import.meta bug (#​14286)

v5.1.16

Compare Source

Patch Changes

• fix: don't wrap pseudo classes inside :global(...) with another :global(...) during migration (#​14267)

• fix: bail on named slots with that have reserved keywords during migration (#​14278)

v5.1.15

Compare Source

Patch Changes

• fix: consider static attributes that are inlined in the template (#​14249)

v5.1.14

Compare Source

Patch Changes

• fix: migration script messing with attributes (#​14260)

• fix: do not treat reassigned synthetic binds as state in runes mode (#​14236)

• fix: account for mutations in script module in ownership check (#​14253)

• fix: consider img with loading attribute not static (#​14237)

v5.1.13

Compare Source

Patch Changes

• fix: add migration task when there's a variable named that would conflict with a rune (#​14216)

• fix: consider valueOf in the reactive methods of SvelteDate (#​14227)

• fix: handle sibling combinators within :has (#​14213)

• fix: consider variables with synthetic store sub as state (#​14195)

• fix: read index as a source in legacy keyed each block (#​14208)

• fix: account for shadowing children slot during migration (#​14224)

• fix: ensure explicit nesting selector is always applied (#​14193)

• fix: add lang="ts" attribute during migration if needed (#​14222)

v5.1.12

Compare Source

Patch Changes

• fix: ignore as type expressions on property definitions (#​14181)

• fix: restore active reaction if then block throws (#​14191)

• chore: adds legacy mode flag reducing bundle size in runes mode only apps (#​14180)

v5.1.11

Compare Source

Patch Changes

• fix: error on TypeScript's readonly modifier (#​14153)

• fix: remove scoping for :not selectors (#​14177)

v5.1.10

Compare Source

Patch Changes

• fix: ensure non-matching elements are scoped for :not(...) selector (#​13999)

• fix: ensure video elements autoplay in safari (#​14095)

• fix: ensure trailing multiline comments on props produce correct code (#​14143#issuecomment-2455702689) (#​14143)

• fix: correctly infer <a> tag namespace (#​14134)

• fix: check options namespace for top level svelte:elements (#​14101)

• fix: ensure migrate keeps inline/trailing comments in $props type definition (#​14143)

• fix: update links in JSDoc (#​14165)

• fix: ensure SvelteMap and SvelteSet work with generators in dev (#​14103)

• fix: only output the key for each_key_duplicate (#​14147)

• fix: prevent migrated snippet from shadow snippet prop (#​14127)

• fix: pass along anchor in legacy class wrappers (#​14100)

• fix: recognize all custom element prop definitions (#​14084)

• fix: migrate multiple declarations with only some exported correctly (#​14126)

---

Configuration

📅 Schedule: Branch creation - "before 2pm on Monday" in timezone Europe/London, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
unplugin-typia-nextjs	⬜️ Ignored (Inspect)	Visit Preview		Nov 27, 2024 7:00pm

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@sveltejs/[email protected]	environment	+1	84.9 kB	svelte-admin
npm/@sveltejs/[email protected]	environment	0	8.55 kB	svelte-admin
npm/@sveltejs/[email protected]	environment, eval Transitive: filesystem	+16	1.07 MB	svelte-admin
npm/@sveltejs/[email protected]	None	+3	192 kB	svelte-admin
npm/[email protected]	None	0	56.2 kB	oxalorg
npm/[email protected]	None	+41	13.3 MB	antfu, octref, orta, ...1 more
npm/[email protected]	Transitive: environment, eval, filesystem	+19	5.34 MB	svelte-language-tools-deploy
npm/[email protected]	None	+8	3.21 MB	conduitry, rich_harris, svelte-admin

🚮 Removed packages: npm/@webpack-cli/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Possible typosquat attack	npm/[email protected]	Did you mean: emoji-regex~~-xs~~	examples/sveltekit/package.json	⚠︎

View full report↗︎

Next steps

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]