yarn install --mutex network:42424 --non-interactive
See original GitHub issueExpected Behavior
Current Behavior
Possible Solution
Steps to Reproduce (for bugs)
lerna.json
<!-- Please paste your `lerna.json` here -->
lerna-debug.log
<!-- If you have a `lerna-debug.log` available, please paste it here -->
<!-- Otherwise, feel free to delete this <details> block -->
Context
Your Environment
Executable | Version |
---|---|
lerna --version |
VERSION |
npm --version |
VERSION |
yarn --version |
VERSION |
node --version |
VERSION |
OS | Version |
---|---|
NAME | VERSION |
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5
Top Results From Across the Web
lerna ERR! yarn install --mutex network:42424 --non ... - GitHub
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. lerna ERR! yarn install --mutex network:42424 --non-interactive stderr: ...
Read more >lerna ERR! yarn install --mutex network:42424 --non-interact
Hello everyone as promised, the title speaks for it's self. I give you my take on how I resolved the issue.I'm in to...
Read more >freesewing/development - Gitter
... only Usage: yarn [options] yarn: error: no such option: --mutex lerna ERR! yarn install --mutex network:42424 --non-interactive --no-package-lock exited ...
Read more >yarn install --mutex network:42424 --non-interactive exited 1 in ...
lerna ERR! yarn install --mutex network:42424 --non-interactive exited 1 in 'root' npm ERR! root@ install: lerna bootstrap.
Read more >terminal defaults to old yarn version (lerna bootstrap)
For me, this was happening in Ubuntu 20.04 , and it solved with unistalling cmdtest: sudo apt-get purge cmdtest.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
At my lerna.json, this fixed it
Hi Folks 👋
You may or may not know that lerna is now under the stewardship of Nrwl (announcement here https://github.com/lerna/lerna/issues/3121), a company with a long history of not just producing valuable open-source software (OSS), but also backing others (at the time of writing, Nrwl has donated over $50,000 to OSS it hasn’t created, see https://opencollective.com/nx for full details).
Quite simply, Nrwl ❤️ OSS, and is committed to making lerna the best it can be. We use it ourselves.
We hope you will continue to be a part of this community as we look to take things forward from here!
Please see https://github.com/lerna/lerna/discussions/3140 for more details on our plans for 2022.
In the case of this specific issue, no information has been provided to assist with looking into the problem. Please kindly head over to https://github.com/lerna/repro and apply any minimal changes necessary to reproduce the behavior.
Many thanks 🙏