build(deps-dev): Bump vitest and @vitest/coverage-v8 #225
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
dependencies
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/vitest-and-vitest/coverage-v8-1.2.2
branch
2 times, most recently
from
c529805 to
b310285
Compare
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) and [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8). These dependencies needed to be updated together. Updates `vitest` from 0.33.0 to 1.2.2 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v1.2.2/packages/vitest) Updates `@vitest/coverage-v8` from 0.34.6 to 1.2.2 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v1.2.2/packages/coverage-v8) --- updated-dependencies: - dependency-name: vitest dependency-type: direct:development update-type: version-update:semver-major - dependency-name: "@vitest/coverage-v8" dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/vitest-and-vitest/coverage-v8-1.2.2
branch
from
b310285 to
1caa450
Compare
|
@jbergstroem any idea how to fix the typing issue? Seem to be related to how packages are released now. Also the coverage dropped a lot. |
|
I will take a look when I have a moment |
Looked into this - we're falling behind a bit on a lot of deps (which has major / breaking updates). I think the best way forward is probably refactoring things a bit for the test harness (I recall talking about this a while ago) - use the vite builtin server instead of express and update the mocks in msw ( The coverage drop is due to having no coverage for |
|
@jbergstroem Thanks for the investigation. That would be a major refactor as currently those e2e tests are run manually. We would need to change the tests to be run automatically (ideally in browser mode) and then we would be able to use mws. What I don't get is that compiling an express app should still work. |
I already started locally; low prio but I think having playwright running the tests is the way to go. That way, we can also cover multipe browsers, phones, etc.
Yeah; I can look at that specifically today. |
|
Superseded by #233. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/vitest-and-vitest/coverage-v8-1.2.2
branch
Bumps vitest and @vitest/coverage-v8. These dependencies needed to be updated together.
Updates
vitestfrom 0.33.0 to 1.2.2Release notes
Sourced from vitest's releases.
... (truncated)
Commits
b1462a4chore: release v1.2.26689856fix(coverage): don't crash when re-run removes earlier run's reports (#5022)fff1a27fix(vitest): don't throw an error if mocked file was already imported (#5050)6dae3fefix(typecheck): fixignoreSourceErrorsin run mode (#5044)cf5641afix(vitest): support older NodeJS with asyncimport.meta.resolve(#5045)915d6c4fix(threads): mention common work-around for the logged error (#5024)a9a486ffix(vitest): allowuseFakeTimersto fakerequestIdleCallbackon non brows...253df1cfix(vitest): throw an error if vi.mock is exported (#5034)7344870feat(vitest): expose getHooks & setHooks (#5032)9c7c0fcfix(vitest): test deep dependencies change detection (#4934)Updates
@vitest/coverage-v8from 0.34.6 to 1.2.2Release notes
Sourced from
@vitest/coverage-v8's releases.... (truncated)
Commits
b1462a4chore: release v1.2.2d53b858fix(coverage): removecoverage/.tmpfiles after run (#5008)6421c27chore: release v1.2.14b41131fix(coverage):thresholds.autoUpdateto work with arrow function configurat...b561c32chore: release v1.2.096dc6e9feat(coverage): custom reporter support (#4828)a73c1c2chore: release v1.1.3be5a259chore: release v1.1.2c8abbc1chore: release v1.1.19497f48chore: release v1.1.0Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)