Issue with deploying a project using yarn instead of npm, resolved by adding a configuration to lerna.json file.

Having a strange deploy issue on a new project.
I'm using yarn instead of npm, so I deleted any of the package-lock files already. I get this error when deploying after most of the process goes smoothly:


348 PM: 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.
I do have yarn.lock files that have a version of 1 at the top of them, so I can't figure out why this isn't sufficient.

Any thoughts of things to try?

It looks like that error comes from cipm, which I think requires a package-lock.json file (not a yarn.lock file). When you deleted package-lock.json did you also rimraf or delete node_modules? Where are you deploying?

i was having a lot of dependency issues so I deleted the cache/node_modules/package-lock at some point and restarted fresh with yarn

the deployment is the auto-setup one with netlify from the gatsby/sanity demo project

Did you first try to use NPM to deploy? In that case, your Netlify build settings may still be configured with NPM.

I suppose that's the default? This is the first time since the initial setup process that I'm trying to deploy.

Did you first try to use NPM to deploy? In that case, your Netlify build settings may still be configured with NPM.

There might be something helpful here: https://docs.netlify.com/configure-builds/manage-dependencies/#javascript-dependencies

It looks like that error comes from cipm, which I think requires a package-lock.json file (not a yarn.lock file). When you deleted package-lock.json did you also rimraf or delete node_modules? Where are you deploying?

i was having a lot of dependency issues so I deleted the cache/node_modules/package-lock at some point and restarted fresh with yarn

the deployment is the auto-setup one with netlify from the gatsby/sanity demo project

Figured it out! Thanks for the effort Geoff.
So, initially the build process was auto-detecting yarn and installing packages with yarn, but then when running 'lerna bootstrap' it defaults to npm.

The solution was to add '"npmClient": "yarn",' to my lerna.json file in my root directory.

Great! Glad you got it working. 🙂