[NO-JIRA] Bump lerna from 5.1.8 to 8.1.5 (palindromic upgrade) #235
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
f03f9d8
Bump lerna from 5.1.8 to 8.1.5 (palindromic upgrade)lerna bootstrap
is replaced withyarn install
post lerna v7 [1],and since this was leveraged in a postinstall script we can (and should) just
remove, as otherwise now
yarn install
will recursively install, forever.lerna link
is no longer necessary post lerna v7, as packagelinking is done automagically as part of the
yarn install
process [2], so weshould just delete any occurrences of this, such as in the link_dev script.
useWorkspaces key in lerna.json should be removed [3], this is a breaking
change for lerna 7+ that also needs to be made to the project config. Simple
enough, all that is required to just to delete the relevant key from
lerna.json.
[1] https://lerna.js.org/docs/legacy-package-management#:~:text=Replace%20lerna%20bootstrap%20with%20npm%20install%20(or%20yarn/pnpm).%20If%20you%20are%20already%20performing%20your%20package%20manager%27s%20install%20command%20somewhere%20in%20your%20workflow%20before%20where%20you%20had%20previously%20called%20lerna%20bootstrap%2C%20then%20you%20can%20just%20delete%20it%20instead
[2] https://lerna.js.org/docs/legacy-package-management#:~:text=lerna%20link%20can%20just%20be%20removed%2C%20as%20the%20linking%20step%20is%20now%20handled%20by%20your%20package%20manager%20during%20npm%20install.
[3] https://github.com/lerna/lerna/blob/main/CHANGELOG.md#:~:text=Workspaces%20are%20used%20by%20default%20and%20useWorkspaces%20has%20been%20removed
Detail
Bumps lerna to 8.1.5 from 5.1.8.
Checklist