Bump vitest from 0.34.6 to 4.1.2 in /apps/desktop#96
Open
dependabot[bot] wants to merge 1 commit intomainfrom
Open
Bump vitest from 0.34.6 to 4.1.2 in /apps/desktop#96dependabot[bot] wants to merge 1 commit intomainfrom
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
3619704 to
ed40bc0
Compare
ed40bc0 to
497498d
Compare
497498d to
57c5f5f
Compare
57c5f5f to
a26076e
Compare
a26076e to
67547ca
Compare
67547ca to
49851b9
Compare
49851b9 to
a528ec9
Compare
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 0.34.6 to 4.1.2. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.2/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.1.2 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
a528ec9 to
d0e10d1
Compare
|
PR author is in the excluded authors list. |
| "typescript": "^5.7.3", | ||
| "vite": "^8.0.3", | ||
| "vitest": "^0.34.6", | ||
| "vitest": "^4.1.4", |
There was a problem hiding this comment.
[🟡 Medium] [🟡 Investigate]
The vitest config specifies coverage.provider: "v8" and package.json has a test:coverage script (vitest run --coverage). In vitest 0.34.x, the v8 coverage provider was bundled. In vitest 4.x, it is a separate peer dependency (@vitest/coverage-v8) that must be explicitly installed. Since @vitest/coverage-v8 is not in package.json, running npm run test:coverage will fail at runtime with a missing provider error.
// apps/desktop/package.json
"vitest": "^4.1.4"Vitest 4.x's peer deps list @vitest/coverage-v8: 4.1.4 as optional. Add "@vitest/coverage-v8": "^4.1.4" to devDependencies to restore coverage support.
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.
Bumps vitest from 0.34.6 to 4.1.2.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
fc6f482chore: release v4.1.26f97b55feat: disable colors if agent is detected (#9851)b3c992cfix(coverage): correctcoverageConfigDefaultsvalues and types (#9940)7c06598fix: ensure sequential mock/unmock resolution (#9830)f54abadchore: add typo-checker skill and fix typos (#9963)7aa9377fix: don't resolvesetupFilesfrom parent directory (#9960)1f2d318chore: release v4.1.1ebfde79refactor: renamematchesTagsFiltertomatchesTags(#9956)5611500feat(experimental): introduceexperimental.vcsProvider(#9928)eec53d9feat(experimental): exposematchesTagsFilterto test if the current filter ...Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for vitest since your current version.