-
-
Notifications
You must be signed in to change notification settings - Fork 38
feat(vitest): vitest browser mode #588
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
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: ad89510 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
commit: |
if (componentTesting) { | ||
sv.devDependency('@vitest/browser', '^3.2.3'); | ||
sv.devDependency('vitest-browser-svelte', '^0.1.0'); | ||
sv.devDependency('playwright', '^1.0.0'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would suggest picking the highest available playwright minor here, or at least the one that was available when vitest browser mode was introduced, i am not sure playwright 1.0.0 is actually compatible with it (playwright does breaking changes in minors unfortunately)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it matter though? Users should always get the latest minor installed, assuming they havn't used playwright in their project before
Supports
vitest
browser mode. Makes the setup more flexible by asking the user to add component / unit testing.Adds a new
object.createFromPrimitives
to core that should help us find the right balance for #557. We should allobject.create
calls in the future and try to use this wherever possible.todo:
The following Vite config options will be overridden by SvelteKit: - root
is acurate and how to avoid it