Repository navigation
fix: Remove optional vitest peer dependency - #1613
Merged
Merged
Conversation
npm 10 (Node 22 default) fails to install the package with "Cannot read properties of null (reading 'edgesOut')" since vitest 4.1.12. Pinning the peer version does not help; removing it does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
apify-service-account
added
the
tested
RobertCrupa
approved these changes
Oct 16, 2026
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
3 participants
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.
Since vitest 4.1.12 (2026-10-15),
npm install/npx @apify/actors-mcp-serverfails on npm 10, the default npm on Node 22:Cannot read properties of null (reading 'edgesOut'). 0.18.3 is affected too, and it's why the beta smoke tests are red. npm 11 and pnpm work.The trigger is our optional
vitestpeer, which exists only for the./test-kitexport. Pinning it to an exact version doesn't help. Removing it does. Tested by installing the packedpackage.jsonwith npm 10.9.9.apify-mcp-server-internalalready hasvitestas its own dev dependency, so no change is needed there.AI-assisted (Claude Code).
🤖 Generated with Claude Code