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

chore(deps): update dependency svelte to ^5.0.0-next.193 #227

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 21, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
svelte (source) ^5.0.0-next.165 -> ^5.0.0-next.193 age adoption passing confidence

Release Notes

sveltejs/svelte (svelte)

v5.0.0-next.193

Compare Source

Patch Changes
  • fix: improve validation error that occurs when using {@​render ...} to render default slotted content (#​12521)

  • fix: reset hydrate node after hydrate(...) (#​12512)

v5.0.0-next.192

Compare Source

Patch Changes
  • fix: make animations more robust to quick shuffling (#​12496)

  • feat: warn if binding to a non-reactive property (#​12500)

  • fix: ensure $state proxy invokes set accessor if present (#​12503)

v5.0.0-next.191

Compare Source

Patch Changes
  • fix: properly assign trailing comments (#​12471)

  • breaking: remove deep reactivity from non-bindable props (#​12484)

  • fix: ensure async initial store value is noticed (#​12486)

  • fix: don't add imports to hoisted event parameters (#​12493)

  • fix: set volume through DOM property rather than attribute (#​12485)

v5.0.0-next.190

Compare Source

Patch Changes
  • fix: hydrate multiple <svelte:head> elements correctly (#​12475)

  • fix: assign correct scope to attributes of named slot (#​12476)

  • breaking: warn on quoted single-expression attributes in runes mode (#​12479)

v5.0.0-next.189

Compare Source

Patch Changes

v5.0.0-next.188

Compare Source

Patch Changes
  • fix: ensure $state.snapshot never errors (#​12445)

  • feat: move dev-time component properties to private symbols' (#​12461)

v5.0.0-next.187

Compare Source

Patch Changes
  • fix: always pass original component to HMR wrapper (#​12454)

  • fix: ensure previous transitions are properly aborted (#​12460)

v5.0.0-next.186

Compare Source

Patch Changes
  • feat: skip pending block for already-resolved promises (#​12274)

  • feat: add ability to ignore warnings through warningFilter compiler option (#​12296)

  • fix: run animations in microtask so that deferred transitions can measure nodes correctly (#​12453)

v5.0.0-next.185

Compare Source

Patch Changes
  • fix: allow leading and trailing comments in mustache expression (#​11866)

  • fix: ensure hydration walks all nodes (#​12448)

  • fix: prevent whitespaces merging across component boundaries (#​12449)

  • fix: detect mutations within assignment expressions (#​12429)

v5.0.0-next.184

Compare Source

Patch Changes
  • fix: show correct errors for invalid runes in .svelte.js files (#​12432)

  • breaking: use structuredClone inside $state.snapshot (#​12413)

v5.0.0-next.183

Compare Source

Patch Changes
  • fix: properly validate snippet/slot interop (#​12421)

  • fix: cache call expressions in render tag arguments (#​12418)

  • fix: optimize bind:group (#​12406)

v5.0.0-next.182

Compare Source

Patch Changes
  • fix: abort outro when intro starts (#​12321)

  • feat: warn in dev on {@&#8203;html ...} block hydration mismatch (#​12396)

  • feat: only create a maximum of one document event listener per event (#​12383)

  • fix: disallow using let: directives with component render tags (#​12400)

  • fix: mark variables in shorthand style directives as referenced (#​12392)

  • fix: handle empty else if block in legacy AST (#​12397)

  • fix: properly delay intro transitions (#​12389)

v5.0.0-next.181

Compare Source

Patch Changes
  • fix: reflect SvelteURLSearchParams changes to SvelteURL (#​12285)

  • fix: ensure hmr block effects are transparent for transitions (#​12384)

  • feat: simpler HMR logic (#​12391)

v5.0.0-next.180

Compare Source

Patch Changes
  • fix: handle nested :global(...) selectors (#​12365)

  • feat: include CSS in <head> when css: 'injected' (#​12374)

  • fix: destroy effects that error on creation (#​12376)

  • breaking: rename legacy.componentApi to compatibility.componentApi (#​12370)

  • fix: correctly validate <svelte:component> with bind:this (#​12368)

v5.0.0-next.179

Compare Source

Patch Changes
  • fix: ensure $slots returns a record of booleans (#​12359)

  • feat: single-pass hydration (#​12335)

v5.0.0-next.178

Compare Source

Patch Changes
  • fix: reconnected deep derived signals to graph (#​12350)

v5.0.0-next.177

Compare Source

Patch Changes
  • breaking: play transitions on mount by default (#​12351)

  • fix: make <select> <option value> behavior consistent (#​12316)

  • chore: stricter control flow syntax validation in runes mode (#​12342)

  • fix: resolve legacy component props equality for mutations (#​12348)

  • fix: make $state component exports settable (#​12345)

v5.0.0-next.176

Compare Source

Patch Changes
  • fix: correct start of {:else if} and {:else} (#​12043)

  • fix: reverse parent/child order in invalid HTML warning (#​12336)

  • fix: reorder reactive statements during migration (#​12329)

  • feat: better <svelte:element> SSR output (#​12339)

  • chore: align warning and error objects, add frame property (#​12326)

  • fix: ensure $effect.root is ignored on the server (#​12332)

  • fix: enable local transitions on svelte:element (#​12346)

v5.0.0-next.175

Compare Source

Patch Changes
  • fix: correctly compile $effect.root in svelte modules (#​12315)

  • fix: ensure bind:this works with component with no return value (#​12290)

v5.0.0-next.174

Compare Source

Patch Changes
  • fix: bail out of event hoisting when referencing store subscriptions (#​12301)

  • chore: make store initialization logic simpler (#​12281)

  • fix: make props optional during SSR (#​12284)

  • fix: ensure each blocks properly handle $state.frozen objects in prod (#​12305)

  • fix: ensure rest props access on hoisted event handlers works (#​12298)

  • fix: lazily create a derived for each read method on SvelteDate.prototype (#​12110)

v5.0.0-next.173

Compare Source

Patch Changes

v5.0.0-next.172

Compare Source

Patch Changes
  • fix: handle duplicate signal dependencies gracefully (#​12261)

v5.0.0-next.171

Compare Source

Patch Changes
  • feat: simpler effect DOM boundaries (#​12258)

v5.0.0-next.170

Compare Source

Patch Changes
  • fix: bump dts-buddy for better type generation (#​12262)

  • breaking: expose CompileError interface, not class (#​12255)

v5.0.0-next.169

Compare Source

Patch Changes
  • breaking: rename svelte/reactivity helpers to include Svelte prefix (#​12248)

  • fix: avoid duplicate signal dependencies (#​12245)

v5.0.0-next.168

Compare Source

Patch Changes
  • fix: ensure HMR doesn't mess with anchor nodes (#​12242)

  • fix: deconflict multiple snippets of the same name (#​12221)

v5.0.0-next.167

Compare Source

Patch Changes
  • fix: make more types from svelte/compiler public (#​12189)

  • fix: support contenteditable binding undefined fallback (#​12210)

  • breaking: prevent usage of arguments keyword in certain places (#​12191)

  • fix(types): export CompileResult and Warning (#​12212)

  • fix: ensure element dir properties persist with text changes (#​12204)

  • fix: disallow accessing internal Svelte props (#​12207)

  • fix: make media bindings more robust (#​12206)

  • fix: allow slot attribute inside snippets (#​12188)

  • feat: allow let props = $props() and optimize prop read access (#​12201)

  • feat: improve type arguments for Snippet and $bindable (#​12197)

v5.0.0-next.166

Compare Source

Patch Changes
  • fix: remove correct event listener from document (#​12101)

  • fix: correctly serialize object assignment expressions (#​12175)

  • fix: robustify migration script around indentation and comments (#​12176)

  • fix: improve await block behaviour in non-runes mode (#​12179)

  • fix: improve select handling of dynamic value with placeholders (#​12181)


Configuration

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

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, 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.

Copy link

vercel bot commented Jul 21, 2024

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 Jul 24, 2024 4:10pm

Copy link

coderabbitai bot commented Jul 21, 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.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

@renovate renovate bot force-pushed the renovate/svelte-5.x branch 2 times, most recently from 70db7a0 to d55d31f Compare July 22, 2024 17:40
Copy link

socket-security bot commented Jul 22, 2024

@renovate renovate bot force-pushed the renovate/svelte-5.x branch 2 times, most recently from 47f38c8 to 9b4ac99 Compare July 23, 2024 22:42
@renovate renovate bot changed the title chore(deps): update dependency svelte to ^5.0.0-next.192 chore(deps): update dependency svelte to ^5.0.0-next.193 Jul 23, 2024
Copy link

socket-security bot commented Jul 23, 2024

🚨 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 NoteSourceCI
Install scripts npm/[email protected]
  • Install script: postinstall
  • Source: echo "[svelte-preprocess] Don't forget to install the preprocessors packages that will be used: sass, stylus, less, postcss & postcss-load-config, coffeescript, pug, etc..."
🚫
Install scripts npm/@sveltejs/[email protected]
  • Install script: postinstall
  • Source: node postinstall.js
🚫

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

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

@renovate renovate bot force-pushed the renovate/svelte-5.x branch 3 times, most recently from 4894744 to f2ec638 Compare July 24, 2024 15:53
@renovate renovate bot force-pushed the renovate/svelte-5.x branch from f2ec638 to 6f1a309 Compare July 24, 2024 16:10
@ryoppippi ryoppippi closed this Jul 24, 2024
Copy link
Contributor Author

renovate bot commented Jul 24, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (^5.0.0-next.193). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/svelte-5.x branch July 24, 2024 16:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant