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 @sveltejs/vite-plugin-svelte to v5 #57

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 27, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sveltejs/vite-plugin-svelte (source) ^3.0.0 -> ^5.0.0 age adoption passing confidence

Release Notes

sveltejs/vite-plugin-svelte (@​sveltejs/vite-plugin-svelte)

v5.0.1

Compare Source

Patch Changes
  • Fix peer dependencies warning (#​1038)

v5.0.0

Compare Source

Major Changes
  • Handle Vite 6 breaking change and remove Vite 5 handling (#​1020)

  • Support Vite 6 (#​1026)

Minor Changes
  • Add esm-env to ssr.noExternal by default to resolve its conditions with Vite (#​1020)

  • Support ?inline query on Svelte style virtual modules (#​1024)

Patch Changes

v4.0.2

Compare Source

Patch Changes
  • Allow script tags to span multiple lines (5309d7b)

v4.0.1

Compare Source

Patch Changes
  • removed references to compiler options no longer available in svelte5 (#​1010)

v4.0.0

Compare Source

Major Changes
  • only prebundle files with default filenames (.svelte for components, .svelte.(js|ts) for modules) (#​901)

  • remove support for Svelte 4 (#​892)

  • breaking(types): some types that have been unintentionally public are now private (#​934)

  • disable script preprocessing in vitePreprocess() by default because Svelte 5 supports lang=ts out of the box (#​892)

  • replaced svelte-hmr with Svelte 5 compiler hmr integration (#​892)

Minor Changes
  • allow infix notation for svelte modules (#​901)

    Previously, only suffix notation .svelte.js was allowed, now you can also use .svelte.test.js or .svelte.stories.js.
    This helps when writing testcases or other auxillary code where you may want to use runes too.

  • feat(config): dynamically extract list of svelte exports from peer dependency so that new exports work automatically" (#​941)

  • feat(warnings): change default loglevel of warnings originating from files in node_modules to debug. To see them call DEBUG:vite-plugin-svelte:node-modules-onwarn pnpm build. (#​989)

Patch Changes
  • fix: make defaultHandler a required argument for onwarn in plugin options (#​895)

  • prebundle with dev: true by default (#​901)

  • fix(dev): compile with hmr: false for prebundled deps as hmr does not work with that (#​950)

  • fix: ensure svelte modules correctly run in DEV mode (#​906)

  • ensure consistent use of compileOptions.hmr also for prebundling (#​956)

  • fix(optimizeDeps): avoid to optimise server only entrypoints of svelte that are never used on the client (#​941)

  • update peer on workspace packages to avoid packages bumping each other (#​916)

  • export PluginOptions interface (#​976)

  • Remove log about experimental status of Svelte 5. Note that breaking changes can still occur while vite-plugin-svelte 4 is in prerelease mode (#​894)

  • fix: ensure vite config is only resolved once during lazy init of vitePreprocess (#​912)

  • fix(vitePreprocess): default to build config so that svelte-check does not trigger dev-only plugins (#​931)

  • fix: only apply infix filter to basename (#​920)

  • fix: disable hmr when vite config server.hmr is false (#​913)

  • fix(dev): make sure custom cssHash is applied consistently even for prebundled components to avoid hash mismatches during hydration (#​950)

  • Updated dependencies [22baa25, 49324db, e9f048c, 213fedd]:


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

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
Contributor

coderabbitai bot commented Nov 27, 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants