Can you delete package-lock.json > Regenerate using npm i and then push to see if it resolved?

I tried deleting package-lock.json, re-running npm install, and pushing again (also made a small change to .gitignore to trigger redeployment), but unfortunately the deployment is still failing with the same error:

1
npm error Invalid Version:

Thanks!

1
[13:45:05.383] Running build in Washington, D.C., USA (East) – iad1
2
[13:45:05.384] Build machine configuration: 2 cores, 8 GB
3
[13:45:05.442] Cloning github.com/manishdashsharma/auth-flow (Branch: main, Commit: 5bc9da1)
4
[13:45:05.567] Previous build caches not available
5
[13:45:05.725] Cloning completed: 282.000ms
6
[13:45:06.023] Running "vercel build"
7
[13:45:07.030] Vercel CLI 44.6.4
8
[13:45:08.048] Installing dependencies...
9
[13:45:09.224] npm error Invalid Version: 
10
[13:45:09.225] npm error A complete log of this run can be found in: /vercel/.npm/_logs/2025-08-01T08_15_08_411Z-debug-0.log
11
[13:45:09.261] Error: Command "npm install" exited with 1
12
[13:45:09.706] ```

I don't see the new package-lock.json unfortunately: https://github.com/manishdashsharma/auth-flow/commits/main/package-lock.json. It's still 3 hours old

GitHub

History for package-lock.json - manishdashsharma/auth-flow

A simple authentication flow where users sign up, the system checks for an existing profile, creates one if it doesn’t exist, and grants access to the dashboard. - History for package-lock.json - m...

https://github.com/manishdashsharma/auth-flow/commits/main/

GitHub

Commits · manishdashsharma/auth-flow

A simple authentication flow where users sign up, the system checks for an existing profile, creates one if it doesn’t exist, and grants access to the dashboard. - Commits · manishdashsharma/auth-flow

Did you generate package-lock using npm i? It should have more changes than just a version number:

Btw, your project is also failing to build on local:

This what i did The build is now ok

Still the same issue

That is due to to package-lock.json. SInce you aren't generating package-lock.json properly. Could you remove it entirely from your repo and try ?

Let me try but , i didn't i am not generating the package-lock.json properly? npm i is the command right ?

Yes it is the command but as you can see your commit didn't have any change related to package-lock.json https://github.com/manishdashsharma/auth-flow/commit/c6be162cd74c98b67e635823f47457b08330d514

GitHub

Build issue · manishdashsharma/auth-flow@c6be162

A simple authentication flow where users sign up, the system checks for an existing profile, creates one if it doesn’t exist, and grants access to the dashboard. - Build issue · manishdashsharma/auth-flow@c6be162

Removing the package-lock.json worked , Thank you but i still have the same question why it is happening , the package lock is not changing

check if you have package-lock.json excluded using .gitignore or something. If you deploy using Vercel CLI, it should work as well.