test: migrate core tests to vitest - #708
Merged
Merged
Conversation
|
43081j
force-pushed
the
vitest-core
branch
2 times, most recently
from
June 29, 2025 21:37
5c7520e to
039b755
Compare
JoviDeCroock
approved these changes
Jun 30, 2025
JoviDeCroock
left a comment
JoviDeCroock
left a comment
Member
There was a problem hiding this comment.
We could just add it temp if you like
Contributor
Author
|
that'd be helpful i think, and can drop it in the overall merge |
JoviDeCroock
force-pushed
the
vitest-migration
branch
from
June 30, 2025 08:51
633f243 to
25f4e01
Compare
Member
|
CI should run after rebasing |
Migrates the core package to use vitest.
JoviDeCroock
pushed a commit
that referenced
this pull request
Oct 29, 2025
Migrates the core package to use vitest.
JoviDeCroock
pushed a commit
that referenced
this pull request
Jan 9, 2026
Migrates the core package to use vitest.
JoviDeCroock
added a commit
that referenced
this pull request
Jan 14, 2026
* test: add vitest prep (#707) Adds vitest and associated scripts which will not succeed yet, as we have no projects. * fix: move to using a root vitest config (#713) We were quickly going to end up with too many sub-configs, and all sorts of problems with extending the various configs. This switches to a single root config which globs each of the monorepo packages instead. * test: migrate preact/utils to vitest (#715) * test: migrate preact/utils to vitest This also adds `preact/utils` to the pnpm workspace so it can be resolved properly via `@preact/signals-utils`. * chore: revert workspace change * fix: downgrade to vite 6 and revert the revert * test: migrate signals package to vitest (#710) Migrates the signals package to use vitest browser tests. * test: migrate core tests to vitest (#708) Migrates the core package to use vitest. * test: migrate react tests to vitest (#716) * test: migrate react tests to vitest * test: migrate react-transform to vitest * chore: remove mocha/sinon/chai/karma * fix: add exact import * fix: strongly type mocked components * test: add the sketchy transform back * fix: funky runtime path * fix: resolve signals after runtime * test: map things to places * test: use vitest aliases THIS MAY ACTUALLY WORK! * chore: use react 16 in runtime too * test: use correct vitest coverage globs (#779) * chore: remove unused karma config * test: correct coverage globs * Fix some stragglers * Move to browser * test: de-dupe dependencies & use CDP GC (#786) * chore: de-dupe babel dependencies In the lockfile, we ended up with two versions of babel. This is basically de-duping and dropping one of them. * fix: use vitest assertions * fix: dedupe vite * test: use cdp to force garbage collection --------- Co-authored-by: James Garbutt <43081j@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Migrates the core package to use vitest.
just noticed we won't get CI for these branches 😬 not sure i want to have to change the workflow triggers though 🤔
depends on #713