Ghislain B.

> There's a slight problem with this approach and requiring npm >= 8.3.0 See this version bumping script: https://github.com/pixijs/pixijs/blob/dev/package.json#L34 > > We use a specific version of npm@7 to do...

@weiwei @harrytran998 and everyone else... As a possible alternative, you can use [Lerna-Lite](https://github.com/ghiscoding/lerna-lite), that I forked before Nrwl came in, the commands are the same and I added support for...

duplicate of #1818, I would suggest to read the last [comment](https://github.com/lerna/lerna/issues/1818#issuecomment-1161974302) I wrote which might be helpful. Also it's not a good idea to have the `--use-workspaces` flag since that...

as mentioned by original Lerna's author in this recent [comment](https://github.com/lerna/lerna/discussions/3140#discussioncomment-3033079) `bootstrap` should be deprecated in the future, basically you don't need `lerna bootstrap` anymore since all package managers support workspaces...

same goes for npm 8, you don't need bootstrap, declare your `workspaces` in `package.json` and you can also add `--use-workspaces` with npm (as shown in this [npm workspaces](https://docs.npmjs.com/cli/v8/using-npm/workspaces#defining-workspaces) docs), it...

When using Lerna, you must have a `package.json` in the project root (where you add Lerna as devDependency) and also have `package.json` files in each of your monorepo packages (these...

you have `useWorkspaces` set to true, so I assume that it will follow the `workspaces` that is defined in your `package.json` and completely ignore the `packages` set in `lerna.json`

It might have been fixed in `v5.4.0`, see this [comment](https://github.com/lerna/lerna/issues/3261#issuecomment-1208181095). If it's still a problem, then it might be related to this other open issue #3233 with a possible solution...

Hey everyone, this was implemented in Lerna-Lite release [1.2.0](https://github.com/ghiscoding/lerna-lite/releases/tag/v1.2.0) if that interests you. Cheers and happy coding

@simllll perhaps the new ~PR #3262 from today has something to do with your issue?~ (unrelated) EDIT The solution is really the PR #3234 that @simllll opened, it does fix...