Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

lockfile doesn't update the version of dependant packages

See original GitHub issue

Expected Behavior

package-lock.json file of dependant packages should be updated with the correct version when commiting the lock files to git repo. For example, when publishing two packages A and B where A depends on B. When B is updated, A’s package lock should update it’s version and also B’s version

Current Behavior

Only A’s version is updated.

lerna.json

{
  "packages": [
    "packages/*"
  ],
  "version": "independent",
  "command": {
    "version": {
      "message": "chore(release): [skip ci] publish new versions"
    }
  }
}

Context

Need to run npm i to generate the correct lock files and manually commit them.

Executable	Version
`lerna --version`	3.15.0
`npm --version`	6.2.0
`node --version`	v10.9.0

OS	Version
macOS Mojave	10.14.6

Issue Analytics

State:
Created 4 years ago
Reactions:5
Comments:5

Top GitHub Comments

1reaction

liranhershkocommented, Jul 30, 2020

Have a look at https://github.com/lerna/lerna/issues/1415#issuecomment-455790478 There seems to be a workaround.

0reactions

github-actions[bot]commented, Jun 17, 2022

Hi Folks 👋

You will have seen in our message above that we at Nrwl are working really hard to bring the lerna repo up to date with what matters most to its community in June 2022.

As previously stated in that message, because we have not heard from the original author of this issue within the last 14 days, we are now automatically closing it.

If any users, including the original author, are still impacted by this issue then we still want to hear from you!

All we ask is that you first update to the latest lerna (5.1.4 at the time of writing) to make sure it is still reproducible, and then fill out one of our new issue templates, providing all the requested details which apply to your situation:

https://github.com/lerna/lerna/issues/new/choose

Many thanks again! 🙏

P.S. Over and above getting to grips with the repo, we have also been hard at work launching a new website, resolving all vulnerabilities, merging exciting new features and reigniting community PR contributions! 🚀

You can read our recent blog post to learn more about what we’ve been up to: https://blog.nrwl.io/lerna-5-1-new-website-new-guides-new-lerna-example-repo-distributed-caching-support-and-speed-64d66410bec7

Top Results From Across the Web

yarn.lock file is not updating after I update the version of a ...

I'm updating the version of a particular package from version 2.0.14 to version 2.0.16 . When I do yarn install or just yarn...

Dependency Management With Python Poetry

The update command will update all your packages and their dependencies within their version constraints. Afterward, Poetry will update your poetry.lock file.

Issue with renv.lock file - General - RStudio Community

lock for capturing all dependencies (and their current version at the time the lockfile was generated). In that case, calling poetry add <package>...

Why does package-lock.json exist, and how does it work?

When writing JavaScript applications, you describe its dependencies using a package.json file. This file contains all of your applications ...

Fixing security vulnerabilities in npm dependencies in less ...

Delete your package-lock.json file or for yarn users, delete your yarn.lock file. In an ideal world this would work, but there might be...