forked from vibemafiaclub/argos
-
Notifications
You must be signed in to change notification settings - Fork 0
chore(deps): bump the npm_and_yarn group across 1 directory with 4 updates #40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -51,6 +51,6 @@ | |
| "prisma": "^6", | ||
| "tailwindcss": "^4", | ||
| "typescript": "^5", | ||
| "vitest": "^2.1.9" | ||
| "vitest": "^3.2.6" | ||
| } | ||
| } | ||
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
vitest v3 migration guide breaking changes from v2💡 Result:
Migrating from Vitest v2 to v3 involves several breaking changes and deprecations. Below are the key adjustments required to ensure compatibility. Key Breaking Changes - Test/Describe Arguments: Passing an object as the third argument to test or describe functions is deprecated and will trigger a warning [1][2]. - Mock Reset Behavior: spy.mockReset now restores the original implementation of a function rather than resetting it to a fake noop [1][2]. - Fake Timers: Vitest no longer provides default fakeTimers.toFake options. When vi.useFakeTimers is called, Vitest will automatically mock any available timer-related API (except nextTick), including performance.now [1][2]. - Error Equality: The equality checks for errors in toEqual or toThrowError are more strict. Vitest now compares the name, message, cause, and AggregateError.errors properties [1][2]. - Configuration: Module condition export resolution is not enabled by default on Vite 6 [1][2]. Deprecations and Other Removals - Browser Mode Options: The browser.name and browser.providerOptions options are deprecated and will be removed in Vitest 4. Use the new browser.instances option instead [1][2]. - API Types: The Custom Type and WorkspaceSpec types have been removed or updated [1][2]. - General Cleanup: Various internal types, including those for vitest/reporters, have been cleaned up [1][2]. It is recommended to consult the official Vitest Migration Guide for the most granular details regarding specific API signatures and type changes that may impact your codebase [3][1]. Additionally, note that subsequent releases (e.g., v3.2) have further deprecated features, such as the separate vitest.workspace file in favor of the projects option in the root configuration [4][5].
Citations:
🏁 Script executed:
Repository: Seongho-Bae/argos
Length of output: 3256
🏁 Script executed:
Repository: Seongho-Bae/argos
Length of output: 501
🏁 Script executed:
Repository: Seongho-Bae/argos
Length of output: 501
🏁 Script executed:
Repository: Seongho-Bae/argos
Length of output: 412
🏁 Script executed:
Repository: Seongho-Bae/argos
Length of output: 412
🏁 Script executed:
Repository: Seongho-Bae/argos
Length of output: 426
🏁 Script executed:
Repository: Seongho-Bae/argos
Length of output: 426
🏁 Script executed:
Repository: Seongho-Bae/argos
Length of output: 1069
🏁 Script executed:
Repository: Seongho-Bae/argos
Length of output: 1069
vitest 2.x→3.x 업그레이드 호환성 위험도는 낮아 보이며, vitest 실행으로 최종 확인 필요
vitest v2→v3 마이그레이션 가이드의 대표 브레이킹 포인트(vi.useFakeTimers, spy.mockReset, browser.name/providerOptions, toThrowError/에러 객체 동등성 비교, test/describe의 3번째 인자 object 형태 등)에 해당하는 사용이 packages/cli에서 검색되지 않고, packages/cli/vitest.config.ts도 Node 환경 + include 설정만 있습니다.
다만 다른 변경 사항까지 포함해 실제로는
vitest run으로 테스트 통과 여부를 한 번 확인하세요.🤖 Prompt for AI Agents