Skip to content

chore(deps): update dependency @sveltejs/vite-plugin-svelte to v6 #332

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.

Sign up for GitHub

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

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

chore(deps): update dependency @sveltejs/vite-plugin-svelte to v6 #332

wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 10, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
@sveltejs/vite-plugin-svelte (source) ^3.0.0 -> ^6.0.0 age confidence

Release Notes

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

v6.2.1

Compare Source

Patch Changes

  • fix: remove unscopable global styles warning (#​1223)

  • Remove automatic configuration for rolldownOptions.optimization.inlineConst because latest version of rolldown-vite has it enabled by default. (#​1225)

v6.2.0

Compare Source

Minor Changes
  • feat(rolldown-vite): enable optimization.inlineConst by default to ensure treeshaking works with esm-env in svelte (#​1207)

v6.1.4

Compare Source

Patch Changes

  • fix: allow preprocess plugin to run twice (#​1206)

  • fix(types): update urls to PreprocessorGroup and CompileOptions in type documention (#​1203)

  • replace kleur dependency with builtin node:utils styleText (#​1210)

v6.1.3

Compare Source

Patch Changes
  • fix(api): add api.filter and deprecate api.idFilter to avoid confusing filter.id = idFilter.id assignments when used as hybrid filter in other plugins (#​1199)

v6.1.2

Compare Source

Patch Changes
  • fix: ensure compiled css is returned when reloading during dev with ssr (e.g. SvelteKit) (#​1194)

v6.1.1

Compare Source

Patch Changes
  • fix: ensure compiled svelte css is loaded correctly when rebuilding in build --watch (#​1189)

v6.1.0

Compare Source

Minor Changes
  • feat: add support for the new experimental.async option and apply dynamicCompileOptions when compiling Svelte modules (#​1176)
Patch Changes

  • skip comment blocks when reporting compiler errors that might be caused by a preprocessor issue (#​1166)

  • increase logLevel to info for "no Svelte config found" message (#​1179)

v6.0.0

Compare Source

Major Changes

  • drop support for node18 and update exports map to use default export. cjs is supported via require esm in node 20.19+ (#​1129)

  • Remove experimental "advanced raw queries" feature. Basic File.svelte?raw is still supported. (#​1145)

  • Using the typescript preprocessor now requires a tsconfig.json with verbatimModuleSyntax enabled, eg @​tsconfig/svelte (#​1135)

  • remove support for loading commonjs svelte config files (#​1142)

  • bump vite peer dependency to ^6.3.0 || ^7.0.0 (#​1130)

  • define filters using object hook syntax and optimize the filter for resolveId (#​1132)

    NOTE
    include logic has changed to files matching svelteConfig.include OR svelteConfig.extensions. Previously only files matching both were loaded and transformed.

  • split preprocess and compile into separate plugins (#​1145)

    It allows vite plugins to transform code between preprocess and compile, see docs and is the recommended way to replace plugin.api.sveltePreprocess usage in other vite plugins.
    You can also use vite-plugin-inspect now to inspect the result of svelte.preprocess by checking the transform of vite-plugin-svelte:preprocess

    NOTE
    This can be a breaking change in case you have other plugins besides vite-plugin-svelte transforming your svelte code
    To fix this, read the docs on how to order plugins in relation to preprocess and compile

Minor Changes

  • Add experimental support for rolldown-vite (#​1135)

  • replace esbuild optimizer with rolldown optimizer if rolldown-vite is used (#​1135)

  • add support for loading TypeScript Svelte config files in runtimes that support it (#​1142)

    NOTE
    This change only applies to vite-plugin-svelte.

    To use svelte.config.ts in SvelteKit, with the Svelte VS Code extension or other tools reading the Svelte config file, you have to wait until support is implemented there.

Patch Changes

  • reduce deprecation logging to info and allow disabling it with a flag (#​1158)

  • refactor internal caching to reduce code, memory use and avoid perEnvironmentCache (#​1154)

  • fix: crawl local workspace private packages devDependencies for generating vite config ssr.noExternal (#​1155)

  • log known-issues link when using rolldown-vite (#​1144)

  • use vite environment api internally (#​1145)

  • remove vite7 beta releases from peerDependency range. (#​1151)

  • deprecate plugin.api.sveltePreprocess (#​1145)

v5.1.1

Compare Source

Patch Changes
  • fix: prevent accidental pollution of svelteconfig.extensions (#​1171)

v5.1.0

Compare Source

Minor Changes
  • scope css to js module to enable treeshaking scoped css from unused components. Requires vite 6.2 and svelte 5.26 (#​1092)
Patch Changes
  • add svelte > clsx to optimizeDeps.include to avoid page reload when using vite6 and npm (#​1124)

v5.0.3

Compare Source

Patch Changes
  • fix errorhandling to work with errors that don't have a code property (#​1054)

v5.0.2

Compare Source

Patch Changes
  • adapt internal handling of warning and error code property to changes in svelte5 (#​1044)

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

Compare Source

Patch Changes
  • fix errorhandling to work with errors that don't have a code property (1a91581)

v4.0.3

Compare Source

Patch Changes
  • adapt internal handling of warning and error code property to changes in svelte5 (#​1046)

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.
@renovate
Copy link
Contributor Author

renovate bot commented Jul 10, 2025 •
edited
Loading

⚠️ 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: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. npm error code ERESOLVE npm error ERESOLVE unable to resolve dependency tree npm error npm error While resolving: sveltekit-gun-example@1.0.0 npm error Found: svelte@4.2.20 npm error node_modules/svelte npm error dev svelte@"^4.0.0" from the root project npm error npm error Could not resolve dependency: npm error peer svelte@"^5.0.0" from @sveltejs/vite-plugin-svelte@6.2.1 npm error node_modules/@sveltejs/vite-plugin-svelte npm error dev @sveltejs/vite-plugin-svelte@"^6.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 /runner/cache/others/npm/_logs/2025-10-21T18_07_44_309Z-eresolve-report.txt npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-10-21T18_07_44_309Z-debug-0.log
@renovate renovate bot force-pushed the renovate/sveltejs-vite-plugin-svelte-6.x branch from fe246fa to 5f0c15f Compare August 8, 2025 13:51
@renovate renovate bot force-pushed the renovate/sveltejs-vite-plugin-svelte-6.x branch from 5f0c15f to 3e8c7d3 Compare October 21, 2025 18:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant