Conversation
create-fate
@nkzw/fate
@nkzw/fate-indexeddb
react-fate
void-fate
vue-fate
commit: |
This branch has not been deployed
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.
The workspace uses Vite+ 0.3.3. The Vite+ 1.0 toolchain includes Vitest 5 and tsdown 0.23, which change benchmark registration and some defaults.
This change pins the Vite+ 1.0 preview in the pnpm catalog and lockfile. It adds the registry bridge for that preview. The benchmark helper now uses the Vitest 5
benchfixture. Small source changes meet the updated lint rules and keep application behavior.The
example/voidconfig keepsclearMocks: falseto preserve mock call history. Other configs use the Vitest 5 default. Existing pack settings and package exports stay in place.