Error: spawn npm ENOENT

[nr1brolyfan]

When trying to run npx @cloudflare/next-on-pages I get an error

C:\Users\...\...\project>npx @cloudflare/next-on-pages  
@cloudflare/next-to-pages CLI
⚡️
⚡️ Installing 'vercel' CLI...
⚡️
node:events:368
      throw er; // Unhandled 'error' event
      ^

Error: spawn npm ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:282:19)
    at onErrorNT (node:internal/child_process:477:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (node:internal/child_process:288:12)
    at onErrorNT (node:internal/child_process:477:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn npm',
  path: 'npm',
  spawnargs: [ 'install', '-D', 'vercel' ]
}

I use
node@16.13.0 and @18.12.0
npm@8.1.0

[Yoinky3000]

I have already created a pr that can fix this issue, waiting for merge, ref #34

[fineshop]

How can we fix this issue on windows?

[gvatsov]

How can we fix this issue on windows?

I can say that using the @LOLBRUHNICE changes from the quoted PR are working for me on Windows 11.

[surjithctly]

FYI: I'm still getting same error. Looks like its not fixed. Using latest version. cc: @LOLBRUHNICE @dario-piotrowicz

[Yoinky3000]

FYI: I'm still getting same error. Looks like its not fixed. Using latest version. cc: @LOLBRUHNICE @dario-piotrowicz

looks like you are using the pr I previously created, it was closed already, and my latest pr that was merged only solve spawn npx problem and only use npx as well

[surjithctly]

I tried adding npx @cloudflare/next-on-pages@latest @latest flag, but did not work.

Which command I should be using to solve this error?

[dario-piotrowicz]

Hi @surjithctly are you using pnpm?

if so can you delete all pnpm files and try again (just using npx)?

Are you on windows?

[surjithctly]

Yes. I’m using PNPM.

This issue occurs on cloudflare pages build (not local). I’m on Mac.

[dario-piotrowicz]

@surjithctly I've just tried with a fresh new Next.js app (repo)

I think there are some possible solutions:

• remove the pnpm-lock.yaml file (if you want to keep using pnpm locally you could add the file to the gitignore although I don't think it's the best) (f695cc)
• keep your code exactly as is but change the build command in the dashboard, for example by removing the pnpm-lock.yaml file on the fly:
  
• add pnpm as a devDependency (so that the cloudflare builder can find it when needed) (b1ad7a) (this seems the appropriate/cleanest solution to me if you want to keep using pnpm, especially because the previous two solutions don't guarantee you that the same package versions you're using locally are going to be used in production)

Is any of this helpful? 🙂

[surjithctly]

Thanks @dario-piotrowicz adding pnpm as devDep worked.

But I guess this issue should be opened again, because this app should work without that as well.

[dario-piotrowicz]

@surjithctly I'm not sure, I think Cloudflare pages doesn't support pnpm out of the box, as you can for example see
in this conversation and this blogpost.

So I think that currently if you tried using pnpm with any Cloudflare pages app you'd hit the same issue (and if that gets fixed on Cloudflare pages then it will work for next-on-pages as well without any change needed here).

---

Also as you can see from the message, that step comes from the Vercel CLI itself (source) so I think that there isn't much we can do about it on our side anyways.

---

@GregBrimble do you agree?