Lerna bootstrapping root only
See original GitHub issueUnder what circumstances does lerna bootstrap only the root package?
Since a while, lerna bootstrap
doesn’t bootstrap all of the packages, and the below is logged:
lerna info bootstrap root only
-
Moreover, reverting commits (even to those where everything worked) seems to have no impact, and Lerna still bootstraps root only.
-
In new, simple Lerna projects, the same behviour occurs.
-
Trying older Lerna versions did not help.
Unfortunately, the project’s closed source.
{
"packages": ["packages/*"],
"version": "0.0.0",
"useWorkspaces": true,
"npmClient": "yarn",
"npmClientArgs": ["--ignore-engines"]
}
Executable | Version |
---|---|
lerna --version |
3.20.2 |
npm --version |
6.13.7 |
yarn --version |
1.22.4 |
node --version |
v13.11.0 |
| OS | Version | | Ubuntu | 19.10 |
Issue Analytics
- State:
- Created 3 years ago
- Comments:10
Top Results From Across the Web
How *bootstrap root only* work when using local file ... - GitHub
I find lerna is using this mode, but no relevant docs were found. ... How *bootstrap root only* work when using local file...
Read more >Starting with Monorepos using Lerna - Joel H. Gomez Paredes
The next command we gonna use is lerna bootstrap, this command install ... In other part, workspaces only works if your root package.json...
Read more >lerna bootstrap - Fig.io
Bootstrap the packages in the current Lerna repo. Installing all their dependencies and linking any cross-dependencies.
Read more >Facing issues running lerna commands in jenkins pipeline
lerna bootstrap lerna notice cli v3.22.1 lerna info versioning independent lerna info ci enabled lerna info bootstrap root only Error: ...
Read more >Getting Started | Lerna
You can see this configured in the root-level package.json workspaces ... Caching not only restores the terminal output logs, but also artifacts that...
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
I am currently facing this issue, using Lerna
v5.5.1
andnpm
v8.15.0
. Edit: It turns out that I was getting this because I had"useWorkspaces": true
set inlerna.json
, but I am usingnpm
, anduseWorkspaces
is foryarn
. Setting"useWorkspaces": false
fixed the issue. Posting this in case anyone makes the same mistake I did.This issue still exists needs to be re-opened.