@lerna/filter-options
Advanced tools
@lerna/filter-optionsOptions for lerna sub-commands that need filtering
TODO
3.0.0-beta.9 (2018-03-24)
--skip-* properly, leave working tree clean (5b4b2c9)--skip-npm was passed,
despite no actual requirement for that property when no publishing is going on.Now, all publish-related operations are truly skipped with --skip-npm,
and all git commit/push-related operations are skipped with --skip-git.
Passing --skip-npm will now also always push to remote, which represents
a breaking change from 2.x behavior.
Thanks @KingScooty for raising the issue!
bootstrapConfig and publishConfig namespaces are no longer honored.
These config blocks should be moved to command.bootstrap and command.publish, respectively.<a name="3.0.0-beta.8"></a>
FAQs
Options for lerna sub-commands that need filtering
The npm package @lerna/filter-options receives a total of 254,606 weekly downloads. As such, @lerna/filter-options popularity was classified as popular.
We found that @lerna/filter-options 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
Research
An advanced npm supply chain attack is leveraging Ethereum smart contracts for decentralized, persistent malware control, evading traditional defenses.
Security News
Research
Attackers are impersonating Sindre Sorhus on npm with a fake 'chalk-node' package containing a malicious backdoor to compromise developers' projects.
Security News
The npm package for the LottieFiles Player web component was hit with a supply chain attack after a software engineer's npmjs credentials were compromised.