@lerna/package
Advanced tools
Changelog
5.0.0 (2022-05-24)
Lerna workspaces no longer have dependency deprecation warnings.
Node v10.x and v12.x are no longer supported.
Internally npm lifecycle scripts are now invoked using @npmcli/run-script instead of npm-lifecycle in order to modernize the package and fix package vulnerabilities and deprecations.
We are classing this as a breaking change because the APIs of npm-lifecycle and @npmcli/run-script are significantly different, despite @npmcli/run-script being the official successor to npm-lifecycle.
We have successfully made the integration test suite we inherited pass with this change, but there may potentially be aspects related to it which are not covered by the tests and are breaking. If you encounter any issues you believe are related to this change please open a new issue with a dedicated reproduction for us to look into!
Readme
@lerna/packageLerna's internal representation of a package
You probably shouldn't, at least directly.
Install lerna for access to the lerna CLI.
FAQs
Lerna's internal representation of a package
The npm package @lerna/package receives a total of 467,931 weekly downloads. As such, @lerna/package popularity was classified as popular.
We found that @lerna/package demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
A hospital in Mobile, Alabama, agreed to a settlement in a landmark ransomware death lawsuit, but is now reportedly reconsidering the agreement and refusing to pay.
Security News
A new report explores how advancements in LLMs are enhancing cyber threats, including polymorphic malware, personalized spearphishing, and the risk of hijacking customer service bots.
Security News
ESLint has approved an RFC that adds support for TypeScript configuration files, which is aimed at improving the developer experience and recognizing changes in the evolving JavaScript ecosystem.