Deploying Node app fails with package-lock.json but works with yarn.lock

Question

When I try deploying my node.js app with a package-lock.json file, it fails with the error:

flow-library | 09:58:09 Installing node_modules using npm
flow-library | 09:58:12 npm ERR! cipm can only install packages with an existing package-lock.json or npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or later to generate it, then try again.
flow-library | 09:58:12 
flow-library | 09:58:12 npm ERR! A complete log of this run can be found in:
flow-library | 09:58:12 npm ERR!     /home/apps/.npm/_logs/2020-11-12T09_58_12_025Z-debug.log

When I switch over to included a yarn.lock file - the deploy works. I would prefer to stick with npm as that’s what we’re using through-out our project.

Any ideas when cipm complains about the lack of package-lock.json when it definitely exists?

Answer 1

dikshith November 13, 2020

Hello @nickoleary

It appears the commit in that package-lock.json file was missing so you were seeing that npm error. You might have to run npm install and commit the package-lock.json file. Both the NPM and Yarn package managers are supported, however, either package-lock.json for NPM projects or yarn.lock for Yarn projects must be committed to the repo alongside the app’s source code.

We have already documented this under limitation:
https://www.digitalocean.com/docs/app-platform/languages-frameworks/node/

Tip: When submitting any questions related to App Platform please add the tag “DigitalOcean App Platform” which will filter the community questions to App Platform Specialists.

Cheers,

Dikshith

Reply Report

nickoleary November 13, 2020
Hi @dikshith, thanks for the reply and the tip for future questions.

However, I don’t think your answer addresses the problem.

Here is a version of my repository that has a package-lock.json and no yarn.lock file in it: https://github.com/node-red/flow-library/tree/cd3b7b011209e58b24a23f24ac61a3247e75ae96

That failed to deploy as it said the file was missing.

I then pushed this commit: https://github.com/node-red/flow-library/commit/5f781c344df7147f94f565657fe04d49cb71071b that removed the package-lock.json file and added the yarn.lock file.

That deployed successfully.

And is completely reproducible.

This commit removes yarn.lock and adds package-lock.json: https://github.com/node-red/flow-library/commit/dcb1876e28e0f3e5d11f5e427d0c9aabde098b08 - it failed to deploy with the same error

This commit switched back to yarn.lock and removes package-lock.json - https://github.com/node-red/flow-library/commit/f3b528012d649ca126e14549dc97036056e288af - and it successfully deployed.

So there is definitely something going on here.
Reply Report
- dikshith November 13, 2020
  
  Hello @nickoleary
  
  Looks like one of the known issues related to gitignore bug. Our team is working on some workaround and it’s in the testing phase. I would recommend you reach out to our support team for a detailed review and workaround.
  
  Best,
  
  Dikshith
  
  Reply Report
- dikshith November 13, 2020
  
  Hello @nickoleary
  
  Actually, We completed the testing and our workaround is live! I would request you to give it another try and hopefully, it will work now.
  
  Cheers,
  
  Dikshith
  
  Reply Report

Answer 2

nickoleary November 13, 2020
Hi @dikshith, thanks for the reply and the tip for future questions.

However, I don’t think your answer addresses the problem.

Here is a version of my repository that has a package-lock.json and no yarn.lock file in it: https://github.com/node-red/flow-library/tree/cd3b7b011209e58b24a23f24ac61a3247e75ae96

That failed to deploy as it said the file was missing.

I then pushed this commit: https://github.com/node-red/flow-library/commit/5f781c344df7147f94f565657fe04d49cb71071b that removed the package-lock.json file and added the yarn.lock file.

That deployed successfully.

And is completely reproducible.

This commit removes yarn.lock and adds package-lock.json: https://github.com/node-red/flow-library/commit/dcb1876e28e0f3e5d11f5e427d0c9aabde098b08 - it failed to deploy with the same error

This commit switched back to yarn.lock and removes package-lock.json - https://github.com/node-red/flow-library/commit/f3b528012d649ca126e14549dc97036056e288af - and it successfully deployed.

So there is definitely something going on here.
Reply Report
- dikshith November 13, 2020
  
  Hello @nickoleary
  
  Looks like one of the known issues related to gitignore bug. Our team is working on some workaround and it’s in the testing phase. I would recommend you reach out to our support team for a detailed review and workaround.
  
  Best,
  
  Dikshith
  
  Reply Report
- dikshith November 13, 2020
  
  Hello @nickoleary
  
  Actually, We completed the testing and our workaround is live! I would request you to give it another try and hopefully, it will work now.
  
  Cheers,
  
  Dikshith
  
  Reply Report

Related

Question

Deploying Node app fails with package-lock.json but works with yarn.lock

Related

Leave a comment

Looking for something else?

Sign up for our newsletter

Related

Question

Deploying Node app fails with package-lock.json but works with yarn.lock

Related

Leave a comment

Related

question

node.js keep stopping. No errors logged.

question

Crontab + Forever + node.js + NPM

question

pm2 not starting my NodeJS web app

question

node.js idler problem with FileZilla

Looking for something else?