Repository navigation
test: run the unit tests with Vitest instead of Jest - #64
Merged
Merged
Conversation
Jest 30's jest-config depends on deepmerge 4.3.1 (GHSA-gcqx-w48m-w2h4), which has no patched release, so the alert could not be cleared while Jest stayed. Vitest's tree audits clean. The specs change only where the APIs differ. `tsc -p tsconfig.spec.json` runs before the tests, because ts-jest used to type-check the specs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
🎉 This PR is included in version 6.0.0-rc.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Clears this repo's only open Dependabot alert: deepmerge GHSA-gcqx-w48m-w2h4 (low, dev). It comes from Jest 30's
jest-config, and deepmerge has no patched release, so no bump or override removes it. Vitest's tree audits clean. Alerts: 1 → 0;npm audit: 6 low → 0.Change
jest.config.jsare gone. Vitest 5 runs the same specs (vitest.config.ts,lib/**/*.spec.ts).jest.*→vi.*,jest-mock'smocked→vi.mocked, and.mockImplementation()→.mockImplementation(() => {}). The top-level `jest.requireActual` becomes `vi.importActual` in a `beforeAll`, because top-level await does not compile under `module: commonjs`. No production code changes.npm testrunstsc -p tsconfig.spec.jsonfirst.glob/minimatchoverrides are dropped: only Jest needed them.Tests
Release effect
None (
test:). Can merge now.🤖 Generated with Claude Code