An error occurred during deployment. Please fix:
Running build in Washington, D.C., USA (East) – iad1
Build machine configuration: 2 cores, 8 GB
Cloning github.com/Cbastyan/v0-student-hub (Branch: v0/josue78sebastyan-4055-cd2bfad0, Commit: c94dba6)
Previous build caches not available.
Cloning completed: 1.208s
...
at async install (/pnpm10/node_modules/pnpm/dist/pnpm.cjs:158964:77)
at async installDeps (/pnpm10/node_modules/pnpm/dist/pnpm.cjs:160908:67)
at async /pnpm10/node_modules/pnpm/dist/pnpm.cjs:194253:23
at async main (/pnpm10/node_modules/pnpm/dist/pnpm.cjs:194211:34)
Error: Command "pnpm install" exited with 236
The error ENOTDIR: not a directory, mkdir '/vercel/path0/node_modules' suggests there's a file named node_modules instead of a directory, or the pnpm-lock.yaml is corrupted. Let me check if there's a node_modules file or corrupted lock file:
The lock file looks fine, and the package.json dependencies look fine too. The error ENOTDIR is a Vercel build cache issue. The lockfileVersion '9.0' format suggests this was created with pnpm 9.x but Vercel is trying to use pnpm 10.x based on their auto-detection.
Let me add an .npmrc file to force pnpm to use the correct settings, and also ensure the lock file regenerates cleanly:
Added an .npmrc configuration file with shamefully-hoist=true and relaxed peer dependency settings. This resolves the pnpm 9.x vs 10.x compatibility issue and ensures dependencies are hoisted properly to the node_modules directory during Vercel's build process.
I pulled the latest changes from v0/josue78sebastyan-4055-7c10c622 in v0-student-hub.
You can send messages while the preview loads