[Feature] lerna --dryrun
See original GitHub issueHi,
Really liking lerna
so far. However I’ve encountered some unexpected behavior that wound up getting pushed to our public repo and published to npm.
I’d like to be able to run lerna publish
to the point of creating the version commit and tag and stop it there so I can inspect what it did before proceeding.
My first thought for an interface for this is:
$ lerna prepublish
... make sure everything's as expected...
$ lerna publish
Where in this case lerna publish
would see that the head revision is a version tag and skip the prepublish
steps.
It might also be nice to have a lerna revert
that’s basically just git reset --hard HEAD^
after verifying that the HEAD
revision is a version commit.
I’d be happy to do the work for this and submit a PR if you’re open to the idea. How does it sound? Ideas for a better interface?
Thanks!
Bo
Issue Analytics
- State:
- Created 8 years ago
- Reactions:93
- Comments:44 (14 by maintainers)
Top GitHub Comments
An alternative way to test what lerna will do is to install a local npm registry and publish to that:
Then use
npm pack <name>
to inspect the tarballs it published.(Updated to use
verdaccio
which is a more up to date fork ofsinopia
.)Oh like a
--dry-run
flag