🦋 Changeset detected

Latest commit: 5622141

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

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

Open in Stackblitz

npm i https://pkg.pr.new/sveltejs/cli/sv@311

npm i https://pkg.pr.new/sveltejs/cli/svelte-migrate@311

commit: 5622141

requires an update to .gitignore for vitest.workspace temporary bundle files, similar to vite.config and vitest.config

depending on which tsconfig is used, vitest.workspace.ts needs to be added to that too

also if this is combined with storybook addon and that addon configures vitest for stories with play functions to become tests too, the code needs to be modified differently.

also if this is combined with storybook addon and that addon configures vitest for stories with play functions to become tests too, the code needs to be modified differently.

For storybook we are just executing npx stoybook init. So there is not much we can change on our side. But we can probably get things rolling. Additionally, csf is currently not setup by that cli.

requires an update to .gitignore for vitest.workspace temporary bundle files, similar to vite.config and vitest.config

Does this file get's generated for you? For me i only see vite.config.ts.timestamp-* being generated, even while running pnpm test. Additionally it seems like vite recently merged a PR that's going to generate those files outside of the project root either way. Looks like this will be a change that will be introduced in vite@6

depending on which tsconfig is used, vitest.workspace.ts needs to be added to that too

Why should this be necessary?

Requires further modifications as pointed out by @dominikg here dominikg/vitest-example-svelte5#1

Requires further modifications as pointed out by @dominikg here dominikg/vitest-example-svelte5#1

those changes are required for vite-6, however given vitest only works with an override (no-go for our cli) or as a beta with that, i suggest we roll back the vite version in our templates to vite-5 until vitest@3 was released and we were able to ensure the config we create actually works.

By the time vitest@3 is out, i hope that users that created projects from now till then can just keep using the setup and update versions. If a breaking change in vitest@3 requires a config change, i wonder if we have the ability to run an upgrade command as well?

If a breaking change in vitest@3 requires a config change, i wonder if we have the ability to run an upgrade command as well?

will settle for a closed issue documenting the error and new config

may have to share the link a few times but we'll catch up

Needs the following things to be done

• use vite@6 in create templates again
• wait for full vitest@3 release