@lerna/npm-install
Advanced tools
Changelog
3.16.0 (2019-07-18)
@evocateur/pacote
(03e4797)githubRelease
config is also remapped from command.publish
namespace (a3d264e), closes #2177--graph-type
option to control packages included in topological sort (#2152) (ae87669), closes #1437--no-verify-access
to prevent checking for account-level 2FA (ce58d8f)--strict
option to enable throwing when --hoist
warns (#2140) (91437b5)@octokit/plugin-enterprise-rest@^3.6.1
(74a3890)@octokit/rest@^16.28.4
(5f09f50)byte-size@^5.0.1
(ed51ddd)conventional-recommended-bump@^5.0.0
(2a0ed60)fs-extra@^8.1.0
(313287f)get-port@^4.2.0
(778ae6a)glob-parent@^5.0.0
(c6bc218)globby@^9.2.0
(d9aa249)import-local@^2.0.0
(14d2c66)is-ci@^2.0.0
(ab2ad83)load-json-file@^5.3.0
(3718cc9)multimatch@^3.0.0
(968b0d7)p-map@^2.1.0
(9e58394)pify@^4.0.1
(f8ee7e6)semver@^6.2.0
(d8016d9)slash@^2.0.0
(bedd6af)write-json-file@^3.2.0
(4fa7dea)--graph
(9457a21), closes #1970npm-lifecycle@^3.1.0
(e015a74)Changelog
3.14.2 (2019-06-09)
--force-local
option (#2104) (c2fb639)Changelog
3.11.0 (2019-02-08)
Changelog
3.8.2 (2019-01-03)
Changelog
3.6.0 (2018-12-07)
--force-local
option (#1807) (25572af), closes #1763npm info
subprocess to libnpm.manifest (65a1d1b)Changelog
3.3.0 (2018-09-06)
<a name="3.2.1"></a>
Changelog
3.0.0 (2018-08-10)
npm pack
experience (627cfc2)npm pack
before npm publish
(8d80b2c)lerna version
from of lerna publish
(#1522) (8b97394), closes #277 #936 #956 #961 #1056 #1118 #1385 #1483 #1494changed: The package names emitted to stdout are no longer prefixed by a "- ", and private packages are no longer displayed by default.
list: The default output of lerna ls
no longer shows version strings or private packages.
The new alias lerna la
resembles the old output, with the addition of relative path to the package
The new alias lerna ll
is a shortcut for the new --long
option
A new --parseable
option has been added to aid magical piping incantations
--preid
now defaults to "alpha" during prereleases:The previous default for this option was undefined, which led to an awkward "1.0.1-0" result when passed to semver.inc()
.
The new default "alpha" yields a much more useful "1.0.1-alpha.0" result. Any previous prerelease ID will be preserved, just as it was before.
--no-verify
is no longer passed to git commit
by default, but controlled by the new --commit-hooks
option:
The previous behavior was too overzealous, and the new option operates exactly like the corresponding npm version option of the same name.
As long as your pre-commit hooks are properly scoped to ignore changes in package.json files, this change should not affect you. If that is not the case, you may pass --no-commit-hooks
to restore the previous behavior.
<a name="3.0.0-rc.0"></a>