pnpm ENOTDIR error on Vercel deployment blocking GitHub merge

v0
, , ,
1

Hello, I have identified with the Vercel deployment log, that a pnpm issue prevents GitHub merge.
I have tested locally in my machine and it worked fine with pnpm…

pnpm: ENOTDIR: not a directory, mkdir ‘/vercel/path0/node_modules’

    at async Object.mkdir (node:internal/fs/promises:856:10)
    
    at async Promise.all (index 0)
    
    at async headlessInstall (/vercel/.local/share/pnpm/.tools/pnpm/10.0.0_tmp_48/node_modules/pnpm/dist/pnpm.cjs:152507:9)
    
    at async _install (/vercel/.local/share/pnpm/.tools/pnpm/10.0.0_tmp_48/node_modules/pnpm/dist/pnpm.cjs:191700:33)
    
    at async mutateModules (/vercel/.local/share/pnpm/.tools/pnpm/10.0.0_tmp_48/node_modules/pnpm/dist/pnpm.cjs:191555:23)
    
    at async install (/vercel/.local/share/pnpm/.tools/pnpm/10.0.0_tmp_48/node_modules/pnpm/dist/pnpm.cjs:191458:45)
    
    at async installDeps (/vercel/.local/share/pnpm/.tools/pnpm/10.0.0_tmp_48/node_modules/pnpm/dist/pnpm.cjs:193330:31)
    
    at async /vercel/.local/share/pnpm/.tools/pnpm/10.0.0_tmp_48/node_modules/pnpm/dist/pnpm.cjs:225361:21
    
    at async main (/vercel/.local/share/pnpm/.tools/pnpm/10.0.0_tmp_48/node_modules/pnpm/dist/pnpm.cjs:225320:34)
    
    at async runPnpm (/vercel/.local/share/pnpm/.tools/pnpm/10.0.0_tmp_48/node_modules/pnpm/dist/pnpm.cjs:225592:5)

Error: Command “pnpm install” exited with 236

That error and any error (it appears), prevents GitHub merging… The user should be able to merge no matter the deployment error.
Oh, and the “Fix with v0 ‘free’, it does not solve that issue and more importantly, it’s not free! It consumes credit.

5

There was a v0 bug fixed last wednesday where the node_modules directory can be left as a symlink during deploy, which is what the error you’re seeing is for

This is fixed for new chats but there are some older chats still affected. Until the fix rolls out to those, are you able to either

  • Duplicate into a new chat and deploy from there
  • or, go to Github and manually merge the PR into main, then create a new chat from main?
2 Likes
7

Still unable to deploy due to that error:
No longer a sandbox issue, but a deployment issue:

ENOTDIR ENOTDIR: not a directory, mkdir ‘/vercel/path0/node_modules’

pnpm: ENOTDIR: not a directory, mkdir ‘/vercel/path0/node_modules’

at async Object.mkdir (node:internal/fs/promises:856:10)

at async Promise.all (index 0)

at async headlessInstall (/pnpm10/node_modules/pnpm/dist/pnpm.cjs:150979:9)

at async tryFrozenInstall (/pnpm10/node_modules/pnpm/dist/pnpm.cjs:159380:60)

at async \_install (/pnpm10/node_modules/pnpm/dist/pnpm.cjs:159174:37)

at async mutateModules (/pnpm10/node_modules/pnpm/dist/pnpm.cjs:159072:23)

at async install (/pnpm10/node_modules/pnpm/dist/pnpm.cjs:158964:77)

at async installDeps (/pnpm10/node_modules/pnpm/dist/pnpm.cjs:160908:67)

Also, it’s not possible to duplicate a chat that’s connected to a GitHub repo, and if I disconnect it, the chat becomes unavailable.

8

Hey! To help debug your v0 project, could you share your v0 chat link?
It looks like https://v0.app/chat/... — you can copy it from your browser’s address bar while in the chat.

You’ll also need to unlist the chat so our team can view it — here’s how: Sharing | v0 Docs

This helps the team reproduce what you’re seeing much faster. Thanks!

10

There was a node_modules file that was not being displayed in the “code” window/file list in V0, I found it by mistake while navigating my files in GitHub. The node_modules file was create by V0 for some reason. Deployment solved.

11

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.