Repository navigation
chore(deps): bump vitest to v5 & happy-dom to 20.9, add vite devDependency - #229
Open
cline-cloud[bot] wants to merge 1 commit into
Open
cline-cloud[bot] wants to merge 1 commit into
cline-cloud[bot] wants to merge 1 commit into
Conversation
…endency Resolves dependabot PRs #227 and #186 in a single change: - vitest ^4.1 -> ^5.0 - happy-dom ^20 -> ^20.9.0 vitest v5 moved vite from a direct dependency to a peer dependency, so vite ^8 is added explicitly as a devDependency to every workspace package that runs vitest (tests/fusion, tests/fusion-node, benchmarks/client, benchmarks/server) via the test catalog.
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
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.
Summary
Resolves all open Dependabot PRs at once and adds the
vitedevDependency that vitest v5 now requires:vitest^4.1(4.1.5)^5.0(5.0.4)happy-dom^20(20.0.11)^20.9.0(20.14.6)vite^8(8.3.4)Closes #227
Closes #186
Why vite is added
vitest v5 moved
vitefrom a direct dependency to a peer dependency (vite: ^6.4.0 || ^7.0.0 || ^8.0.0). Starting with v5 it is no longer pulled in transitively, soviteis now declared explicitly as adevDependency(via thetestcatalog) in every workspace package that runs vitest:tests/fusiontests/fusion-nodebenchmarks/clientbenchmarks/serverThis also satisfies the
vite: *peer requirement ofvite-tsconfig-paths.Changes
pnpm-workspace.yaml—testcatalog:vitest: ^5.0,happy-dom: ^20.9.0, newvite: ^8.\"vite\": \"catalog:test\"to thedevDependenciesof the four test/benchmark packages above.pnpm-lock.yaml.Verification
pnpm install— cleanjust buildequivalents (tsdown) — both packages buildtests/fusion: 16/16 tests pass on vitest 5.0.4 / happy-dom 20.14.6tests/fusion-node: 10/10 tests passbiome lint .— clean;tsc --noEmit— clean