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 v4 #5088

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 20, 2024

This PR contains the following updates:

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

Release Notes

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

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

@renovate renovate bot enabled auto-merge (squash) October 20, 2024 02:55
Copy link
Contributor Author

renovate bot commented Oct 20, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: e2e/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: e2e-tests@0.0.0
npm error Found: svelte@4.2.19
npm error node_modules/svelte
npm error   dev svelte@"4.2.19" from the root project
npm error
npm error Could not resolve dependency:
npm error peer svelte@"^5.0.0-next.96 || ^5.0.0" from @sveltejs/vite-plugin-svelte@4.0.0
npm error node_modules/@sveltejs/vite-plugin-svelte
npm error   dev @sveltejs/vite-plugin-svelte@"4.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-11-11T21_57_08_204Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-11T21_57_08_204Z-debug-0.log

@renovate renovate bot force-pushed the renovate/sveltejs-vite-plugin-svelte-4.x branch 6 times, most recently from 8b6faf0 to e91fbd2 Compare October 23, 2024 22:24
@renovate renovate bot force-pushed the renovate/sveltejs-vite-plugin-svelte-4.x branch 4 times, most recently from 8d30963 to 1ec9b76 Compare October 29, 2024 10:08
@renovate renovate bot force-pushed the renovate/sveltejs-vite-plugin-svelte-4.x branch 8 times, most recently from ffc9b7b to cfe3d0e Compare November 11, 2024 18:00
@renovate renovate bot force-pushed the renovate/sveltejs-vite-plugin-svelte-4.x branch from cfe3d0e to 355d2fd Compare November 11, 2024 21:57
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