Skip to content

fix: regenerate lockfile so npm install doesn't crash on vitest peer set - #94

Open
ShiGaChenTW wants to merge 1 commit into
viperrcrypto:mainfrom
ShiGaChenTW:fix/npm-lockfile-peer-crash
Open

ShiGaChenTW wants to merge 1 commit into
viperrcrypto:mainfrom
ShiGaChenTW:fix/npm-lockfile-peer-crash

Conversation

@ShiGaChenTW

Copy link
Copy Markdown

npm install crashes on a clean clone, so ./start.sh never reaches the dev server.

npm error Cannot read properties of null (reading 'edgesOut')

The stack lands in arborist's #loadPeerSet while resolving the vitest peer graph — vitest → @vitest/browser-playwright@5.0.0 → peer vitest@4.1.11:

TypeError: Cannot read properties of null (reading 'edgesOut')
    at #loadPeerSet (.../arborist/lib/arborist/build-ideal-tree.js:1289:38)
    at async #buildDepStep (.../arborist/lib/arborist/build-ideal-tree.js:904:11)

Regenerated package-lock.json with npm install --legacy-peer-deps. 605 packages install cleanly, ./start.sh then completes end to end: Prisma client generated, both migrations applied, Next.js serving (GET / 200, GET /api/categories 200, GET /api/categorize 200).

Reproduced on macOS 15.5, node v22.22.3, npm v10.9.8.

🤖 Generated with Claude Code

https://claude.ai/code/session_01TfDpnwHQCYi34ob21XDijs

npm 10 arborist crashes with "Cannot read properties of null
(reading 'edgesOut')" resolving the vitest peer set
(@vitest/browser-playwright@5.0.0 -> peer vitest@4.1.11).
Regenerated via `npm install --legacy-peer-deps` so a fresh
clone can run ./start.sh without hitting the crash.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TfDpnwHQCYi34ob21XDijs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant