This looks like a network connectivity issue between Vercel’s build environment and the npm registry. Vercel’s status for builds and npm registry are OK.
So what’s wrong? (everything worked fine on my computer, in Europe/Belgium)
```
[14:05:43.761] Running build in Washington, D.C., USA (East) – iad1
[14:05:43.761] Build machine configuration: 2 cores, 8 GB
[14:05:43.777] Cloning github.com/xxx/xxx (Branch: main, Commit: 28dab63)
[14:05:43.833] Skipping build cache, deployment was triggered without cache.
[14:05:44.605] Cloning completed: 828.000ms
[14:05:45.004] Running “vercel build”
[14:05:45.392] Vercel CLI 45.0.10
[14:05:45.869] Running “install” command: pnpm install…
[14:05:46.519] WARN GET https://registry.npmjs.org/@types%2Fnode error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.
…[lots of the same error]…
```
In the meantime, I managed to deploy via the terminal using vercel deploy first, then vercel --prod. And now it works from the GitHub repo auto-deploy.
I didn’t change anything (just some text in a .tsx file).
Which project? Which URL?
I guess the URL of the Vercel project I created is useless (ex: foo.vercel.app).
My app was a basic clone of Next.js SaaS Starter, with only these changes:
We don’t support pinning packageManager without Corepack unfortunately. Could you try enabling Corepack and let us know if you are still experiencing this issue?