lerna v5

[turadg]

refs: #4660

Description

We might remove Lerna,

• remove Lerna #4660

Meanwhile it's easy to get on a less ancient version. In particular, to get pnpm support. (#8062 tried going all the way to latest, but it changes version numbering behavior.)

No bad breaking changes,
https://github.com/lerna/lerna/blob/main/CHANGELOG.md#400-2021-02-10
https://github.com/lerna/lerna/blob/main/CHANGELOG.md#500-2022-05-24

This had been blocked on these:

• Lerna exec lies/fails to execute command in all packages when there is a cycle lerna/lerna#3242
• package scripts not executed since 5.1.3 lerna/lerna#3233

But those are resolved. See Testing section.

Security Considerations

Documentation Considerations

Testing Considerations

• yarn lerna exec npm pkg get name lists all packages (41)

CI should test the publishing flow.

Previously:

lerna notice cli v5.4.0
lerna info versioning independent
lerna info Executing command in 39 packages: "npm pkg get name"
…
lerna success exec Executed command in 39 packages: "npm pkg get name"

but only 19 packages ran (per yarn lerna exec npm pkg get name |grep ": " | wc -l)

[ghiscoding]

@turadg
Hello I see that you linked your PR to Lerna's issue, just to let you know that the fix proposed in Lerna PR #3234 does work and was applied into this Lerna-Lite PR and that fixed what seems to be the same problem as you and was identified by the Jest team in this issue when they recently switched to Lerna-Lite. I have applied the fix and they are back in business. Since you're contemplating about the possibility to remove Lerna, you should probably take a look at Lerna-Lite, it's much smaller (just install what you need) and the commands are executed the same way so it's easy to migrate (just swap the dependency and you're good to go).

Also note that Lerna v5.3.0+ is now installing Nx behind the scene (want it or not) because they added Nx as a dependency of Lerna, however it remains totally optional in Lerna-Lite (you can read more about Lerna-Lite from the main readme).

Cheers and happy coding

[michaelfig]

Looks like yarn.lock needs regeneration.