I’m writing here since the issue npm install fails with “ENOENT: no such file or directory” has been closed and can only be commented by members.
I’m still experiencing the issue, using latest version npm, but that is not why I’m creating a topic here. I’ll try to create a reproducible repository with firstname.lastname@example.org. As far as I recall the issue is not present in email@example.com.
From my perspective such advice is miss-leading at best. I though
package-lock.json can be used to get re-producible installs of packages i.e. you get the exact same versions across installations regardless of when the installation is executed. If we remove
package-lock.json we’re back to potentially unpredictable installations and thus builds and deployments.