Conversation
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.1keeps this workspace on Vitest 4. This change updates the workspace to a Vite+ 1.0 preview and Vitest 5. The pnpm catalog, overrides, and lockfile now use matching tool versions. The registry setting lets pnpm get the pinned preview build.Vue Test Utils emitted a
decodeEntitieswarning when it compiled string slots with mixed Vue compiler builds. The Nuxt browser test project now resolves@vue/compiler-domthrough Vue's Node entry during dependency optimization. The string slots and strict warning check stay in place. The Nuxt apps keep their build tasks, and the connector keeps its pack settings.