Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency svelte to v5 #212

Merged
merged 1 commit into from
Nov 14, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 23, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
svelte (source) ^4.2.19 -> ^5.1.14 age adoption passing confidence

Release Notes

sveltejs/svelte (svelte)

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)

v5.1.9

Compare Source

Patch Changes
  • fix: ensure transitions are applied to nested elements (#​14080)

v5.1.8

Compare Source

Patch Changes
  • fix: ensure compiler statements are correctly included (#​14074)

v5.1.7

Compare Source

Patch Changes
  • fix: ensure each block inert items are disposed of if the each block is also inert (#​13930)

  • fix: allow warningFilter option for compileModule (#​14066)

  • fix: ensure onMount correctly fires when new expressions are used (#​14049)

  • fix: wrap :id, :where``:not and :has with :global during migration (#​13850)

  • fix: ensure custom element attribute/prop changes are in their own context (#​14016)

v5.1.6

Compare Source

Patch Changes
  • fix: ensure child effects are destroyed before their deriveds (#​14043)

v5.1.5

Compare Source

Patch Changes
  • fix: replace typo in compiler error messages (#​14044)

  • fix: preserve the separator between selectors when an unused selector is in between (#​13954)

  • fix: more robust re-subscribe detection for fromStore (#​13995)

  • fix: allow to pass in TS preference to migration (#​13929)

  • fix: extend derived/state validation error to indirect exports (#​14039)

  • fix: minify inject CSS in prod mode (#​14006)

  • fix: ensure toStore subscription correctly syncs latest value (#​14015)

  • fix: don't access requestAnimationFrame until needed to reduce need for mocks during testing (#​14040)

  • fix: ensure element effects are executed in the correct order (#​14038)

  • fix: make compiler error extend from Error (#​14036)

v5.1.4

Compare Source

Patch Changes
  • fix: add empty stack to CompileDiagnostic to show error on build (#​13942)

  • fix: ensure effect_tracking correctly handles tracking reactions (#​14005)

  • fix: update broken links (#​13944)

  • fix: more exhaustive check during SvelteMap.set in deriveds (#​13951)

  • fix: trim whitespace while migrating blocks (#​13941)

  • fix: update links that previously pointed to preview site (#​14001)

  • fix: properly migrate imports types prefixed with $ (#​14007)

v5.1.3

Compare Source

Patch Changes
  • fix: rethrow errors from await block if no catch block exists (#​13819)

  • fix: ensure SVG element attributes have case preserved (#​13935)

  • fix: ensure bind:group works as intended with proxied state objects (#​13939)

  • fix: ensure value is correctly set to zero on the progress element (#​13924)

  • fix: skip comment nodes in snippet validation logic (#​13936)

  • fix: typo in Action types (#​13874)

  • fix: remove metadata from legacy AST (#​13927)

v5.1.2

Compare Source

Patch Changes
  • fix: improve consistency of transitions (#​13895)

  • fix: enable bound store props in runes mode components (#​13887)

  • fix: ensure each block references to imports are handled correctly (#​13892)

  • fix: ensure SvelteMap reactivity persists through deriveds (#​13877)

  • fix: ensure snippets after empty text correctly hydrate (#​13870)

  • fix: prevent migration script from adding props. to the export let identifier (#​13899)

  • fix: prevent var name clashing for delegated events without params (#​13896)

v5.1.1

Compare Source

Patch Changes
  • fix: internally wrap store subscribe in untrack (#​13858)

  • fix: allow binding to const with spread in legacy mode (#​13849)

  • fix: ensure props internally untracks current_value on sets (#​13859)

  • fix: properly traverse children when checking matches for :has (#​13866)

v5.1.0

Compare Source

Minor Changes
  • feat: export mount() options as the MountOptions type (#​13674)

  • feat: allow usage of getContext() within $derived runes (#​13830)

Patch Changes
  • fix: properly migrate ts with inferred type comments (#​13761)

  • fix: correct property name conversion in custom transitions (#​13820)

  • fix: ensure $effect.tracking returns false inside transition functions (#​13775)

  • fix: migrate default slots to children snippet (#​13760)

  • fix: don't print errors on migration errors (#​13754)

  • fix: prevent spread attribute from overriding class directive (#​13763)

  • fix: ensure :has selectors followed by other selectors match (#​13824)

  • fix: ensure muted DOM property works correctly in FF (#​13751)

  • fix: show filename information in legacy_recursive_reactive_block (#​13764)

v5.0.5

Compare Source

Patch Changes
  • fix: mark :has selectors with multiple preceding selectors as used (#​13750)

  • fix: ensure event context is reset before invoking callback (#​13737)

  • fix: add more robust check for Element prototype (#​13744)

  • fix: do not comment out unused selectors that are inside an unused selector (#​13746)

  • fix: more accurately detect $derived migration opportunities (#​13740)

  • fix: @​debug does not work with proxied-state (#​13690)

  • fix: do not add jsdoc if no types found (#​13738)

v5.0.4

Compare Source

Patch Changes
  • fix: webview preload tag can be any string (#​13733)

  • fix: better children snippet / default slot interop (#​13734)

v5.0.3

Compare Source

Patch Changes
  • chore: ensure transition events are dispatched without current reaction (#​13719)

v5.0.2

Compare Source

Patch Changes
  • fix: don't blank css on migration error (#​13703)

v5.0.1

Compare Source

Patch Changes
  • fix: use typedef for JSDoc props and maintain comments (#​13698)

v5.0.0

Compare Source

A new major version of Svelte has been released! 🎉

The new version brings:

  • even better performance,
  • a more granular reactivity system with runes,
  • more expressive template syntax with snippets and event attributes,
  • native TypeScript support,
  • and backwards compatibility with the previous syntax!

For more details check out the Svelte docs and the migration guide.


Configuration

📅 Schedule: Branch creation - "before 4am on Wednesday" in timezone Europe/Berlin, 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.

🔕 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.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Oct 23, 2024
@renovate renovate bot requested a review from mheob as a code owner October 23, 2024 01:36
Copy link

changeset-bot bot commented Oct 23, 2024

⚠️ No Changeset found

Latest commit: a8840d5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented Oct 23, 2024

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

Name Status Preview Comments Updated (UTC)
eslint-config ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 14, 2024 2:20pm

Copy link

coderabbitai bot commented Oct 24, 2024

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.

Copy link

sonarcloud bot commented Nov 14, 2024

@mheob mheob merged commit 82b6b10 into main Nov 14, 2024
10 checks passed
@mheob mheob deleted the renovate/svelte-5.x branch November 14, 2024 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant