Bump svelte-check from 3.8.4 to 4.1.0 in /frontend

[dependabot]

Bumps svelte-check from 3.8.4 to 4.1.0.

Release notes

Sourced from svelte-check's releases.

svelte-check-4.1.0

• fix: don't move appended content from previous node while hoisting interface (#2596)
• fix: ensure hoisted interfaces are moved after hoisted imports (#2597)
• fix: preserve bind:... mapping on elements for better source maps
• feat: prepare for some upcoming features of Svelte 5

svelte-check-4.0.9

• fix: detect shadowed variables/types during type hoisting (#2590)

svelte-check-4.0.8

• fix: fall back to any instead of unknown for untyped $props (#2582)
• fix: robustify and fix file writing (#2584)
• fix: hoist types related to $props rune if possible (#2571)

svelte-check-4.0.7

• fix: $props: infer types for $bindable, infer function type from arrow function

svelte-check-4.0.6

• chore: autotype const load = ... declarations (#2540)
• chore: provide component instance type in Svelte 5 (#2553)
• chore: support typescript 5.6 (#2545)
• fix: infer object and array shapes from fallback types (#2562)

svelte-check-4.0.5

• fix: include named exports in svelte 5 type (#2528)

svelte-check-4.0.4

• fix: relax component constructor type (#2524)

svelte-check-4.0.3

• breaking(svelte5): only generate function component shape in runes mode (#2517). This means you can no longer just do Component in type positions. Instead you need to prepend it with typeof. Here's how you do it:
  • ...when typing a component instance: Before: let x: Component. After: let x: ReturnType<typeof Component>
  • ...when typing a component constructor/function: Before let x: typeof Component. After let x: typeof Component (no change)
• fix: revert additional two-way-binding checks as they were causing bugs (#2508)
• fix: include files indirectly belonging to a project into correct project (#2488)
• fix: check project files update more aggressively before assigning service (#2518)
• chore: upgrade to chokidar 4 (#2502)

svelte-check-4.0.2

• fix: ensure components typed through Svelte 5's Component interface get proper intellisense

svelte-check-4.0.1

• fix: remove ancient process augmentation from internal d.ts file

svelte-check-4.0.0

• chore: bump magic-string (#2476)
• chore: switch from fast-glob to fdir (#2433)
• fix: detect tag (#2482)
• feat: better type checking for bindings in Svelte 5 (#2477)
• feat: replace svelte-preprocess with barebones TS preprocessor (#2452)

... (truncated)

Commits

• cda5c86 fix: preserve bind:... mapping on elements for better source maps
• be44125 feat: support bind:value={get, set}
• 695c660 chore: bump prettier-plugin-svelte
• 9a5a6af feat: hoist snippets to module context if possible (#2601)
• 050ecc1 chore: consolidate template walking logic (#2600)
• cd1758b feat: support \<svelte:html> (#2599)
• 078f9a0 feat: support \<svelte:bounday> (#2598)
• a1b4a64 fix: ensure hoisted interfaces are moved after hoisted imports (#2597)
• c21de66 fix: don't move appended content from previous node while hoisting interface ...
• b6cac97 fix: use original file path casing for shim files (#2591)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
purplix-io	❌ Failed (Inspect)			Nov 25, 2024 2:55am
purplix-io-iuu9	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 25, 2024 2:55am

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	Transitive: environment, filesystem	+10	5.58 MB	svelte-language-tools-deploy
pypi/[email protected]	None	0	7.71 MB	anthrotype, eustas, google_opensource

🚮 Removed packages: npm/[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
Native code	pypi/[email protected]	Location: Package overview	backend/poetry.lock	🚫
Native code	pypi/[email protected]	Location: Package overview	backend/poetry.lock	🚫
Native code	pypi/[email protected]	Location: Package overview	backend/poetry.lock	🚫
Native code	pypi/[email protected]	Location: Package overview	backend/poetry.lock	🚫
Native code	pypi/[email protected]	Location: Package overview	backend/poetry.lock	🚫
Native code	pypi/[email protected]	Location: Package overview	backend/poetry.lock	🚫
Native code	pypi/[email protected]	Location: Package overview	backend/poetry.lock	🚫

View full report↗︎

Next steps

Why is native code a concern?

Contains native code (e.g., compiled binaries or shared libraries). Including native code can obscure malicious behavior.

Verify that the inclusion of native code is expected and necessary for this package's functionality. If it is unnecessary or unexpected, consider using alternative packages without native code to mitigate potential risks.

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 pypi/[email protected]

[dependabot]

Superseded by #334.