Upgrading - Discrepancies between the Lock Files and Package.json Files

6 replies
Last updated: Jan 21, 2022
Hi team sanity~ It seems like when we run
sanity upgrade
we always end up with discrepencies between the lock files ane the package.json files. Is it always necessary to re
npm install
after each upgrade? Have we always missed a step?
Jan 21, 2022, 1:56 PM
npm lockfile
Jan 21, 2022, 4:39 PM
npm lockfile
Jan 21, 2022, 4:39 PM
Aha! I think that may be the problem. I don't believe the Yarn upgrade command that Sanity runs will affect your npm lockfile. Would it be viable for you to move entirely to Yarn when working with dependencies in your studio project?
Jan 21, 2022, 5:13 PM
Aha! I think that may be the problem. I don't believe the Yarn upgrade command that Sanity runs will affect your npm lockfile. Would it be viable for you to move entirely to Yarn when working with dependencies in your studio project?
Jan 21, 2022, 5:13 PM
We have this in a mono repo uses lerna to execute npms to install all sub repos. We will discuss internally on what to do now we know what is happening πŸ™‚. Thank you so much!
Jan 21, 2022, 5:47 PM
Ah, that makes sense. Let us know if you have any further questions πŸ™‚.
Jan 21, 2022, 5:49 PM

Sanity.io – build remarkable experiences at scale

Sanity is a customizable solution that treats content as data to power your digital business. Free to get started, and pay-as-you-go on all plans.

Categorized in