Conversation
fengmk2
changed the title
e18e dependency analysisNo dependency warnings found. |
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
1 participant
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.
Vite+
0.3.1uses Vitest4.1.11. The Vite+ 1.0 preview uses Vitest5.0.1and changes test defaults.This change pins the preview in the pnpm catalog and lockfile. It updates the package overrides and registry settings. The test projects use Vitest 5 defaults for mock clearing, config inheritance, Vite server sharing, and exact browser locator matches.
The coverage pattern includes source files in nested workspaces under the new glob rules. The Nuxt tests keep
vitestimports because@nuxt/test-utilsrequires that module. The Nuxt browser optimizer uses Vue's Node compiler for runtime templates. This keeps the Vue compiler builds consistent and keeps the accessibility warning check active.