[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live) [v0](/c/v0/59) # Persistent ERR_PNPM_FETCH_404 on Vercel: https: Not Found 471 views · 0 likes · 4 posts Avarela88 7871 (@avarela88-7871) · 2025-06-09 I’m running into a recurring deployment failure on Vercel with both pnpm and npm: ``` ERR_PNPM_FETCH_404 GET https://registry.npmjs.org/https%3A Not Found ``` This error indicates that a malformed URL (`https:`) is being treated as an npm package name. I’ve already: * Cleaned and restored my `package.json` multiple times * Removed any stray dependencies pointing to URLs * Tried both `pnpm install` and `npm install` locally without issues Everything builds fine on my local machine. The problem only appears in the V0/Vercel build environment. It feels like the build infrastructure is generating or injecting that invalid `"https:"` entry at install time, since my GitHub repo’s `package.json` does not contain it. Has anyone experienced a similar issue, or can point me to how Vercel/V0 might be dynamically altering `package.json` during the install step? Any ideas on how to force the build to use the correct file would be greatly appreciated. Jacob Paris (@jacobparis) · 2025-06-11 We don't seem to be doing any manipulation here so unfortunately no extra clues there – a malformed dependency for the https package would be the best explanation Make sure you regenerate your lockfile (if you haven't done that already) Can you share your package.json deps so I can check to see if there's anything suspicious there? JT (@jthole675-9991) · 2025-06-11 I am having the same issue. Have you found a solution? Giacomo Gaglione (@giacomogaglione) · 2025-06-12 me too, same issue. EDIT: confirmed npm incident [npm Status - Issues with package install, package publish, and login.](https://status.npmjs.org/incidents/dn5mcp85737y) 