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
🏁 Script executed:
Repository: lokalise/fastify-extras
Length of output: 2685
🏁 Script executed:
Repository: lokalise/fastify-extras
Length of output: 861
🌐 Web query:
vitest 4.1.0@vitest/coverage-v8compatibility peer dependencies💡 Result:
For Vitest
4.1.0, the@vitest/coverage-v8package you should use is@vitest/coverage-v8@4.1.0, because it declares exact-version peer deps:@vitest/coverage-v8@4.1.0peerDependencies:vitest:4.1.0@vitest/browser:4.1.0(optional)[1]So the compatible pairing is:
vitest@4.1.0+@vitest/coverage-v8@4.1.0[1][2]Install:
npm i -D vitest@4.1.0 `@vitest/coverage-v8`@4.1.0Upgrade
@vitest/coverage-v8to major version 4 to match Vitest 4.Line 86 upgrades
vitestto^4.1.0, but Line 74 keeps@vitest/coverage-v8at^3.2.4. The coverage plugin has exact peer dependency onvitest@4.1.0, making this combination incompatible and breaking coverage runs.Suggested fix
🤖 Prompt for AI Agents