Repository navigation
Add a --preview flag to dry-run np #391
Description
Description
Is the feature request related to a problem?
I'd like to be able to run np in a "dry run" mode more so than what it currently does, np already supports the --no-publish flag to prevent it being published to npmjs.com, I'd also like to prevent any changes being pushed to GitHub, hence a --no-push flag also.
This would allow me to test np completely without pushing or publishing anything remotely to either npmjs.com or github.com.
Possible solution
Follow up with a PR similar to that of ca0f193 where the --no-publish flag was added adding a new CLI option --no-push
Alternatives
IssueHunt Summary
tiagodanin has been rewarded.
Backers (Total: $80.00)
issuehunt ($80.00)
Submitted pull Requests
Tips
- Checkout the Issuehunt explorer to discover more funded issues.
- Need some help from other developers? Add your repositories on IssueHunt to raise funds.
IssueHunt has been backed by the following sponsors. Become a sponsor
Activity
ntwb commentedon Apr 18, 2019
Related: #249/#250
-no-git-tag-versionis similar/close to what I'm asking above, though the PR #250 would still push to GitHub which is what I'd like to avoid.So it would kind of work, but only because (I think) nothing would be committed as the repo would be in a dirty state rather than (what I'd like) is to explicitly not push anything to GitHub
itaisteinherz commentedon Apr 18, 2019
One thing you could do at the moment to achieve this is to avoid setting an upstream branch, which would make
npskip pushing to the remote (however this is obviously a hack, not a solution).Note that this is also related to #386.
itaisteinherz commentedon Apr 18, 2019
Adding a dry run option does sound interesting and useful, though. We could add a
--previewflag which only prints out the changes/actionsnpis going to make without actually doing those.[-]Feature Request: Add a `--no-push` CLI flag to not push Git changes[/-][+]Add a `--preview` flag to dry-run np[/+]IssueHuntBot commentedon May 2, 2019
@IssueHunt has funded $80.00 to this issue.
itaisteinherz commentedon May 8, 2019
I just noticed the
--dry-runflag fornpm publish, which could be useful here.TiagoDanin commentedon May 10, 2019
I don't understand 🤔. Did you mean:
--no-publish?itaisteinherz commentedon May 10, 2019
No, this is what I meant:
TiagoDanin commentedon May 10, 2019
I believe not, because the NP does not show output of NPM.
itaisteinherz commentedon Jun 29, 2019
Maybe we could show parts of the output returned by
npm publish --dry-run, or even the whole output (I'm not sure iflistrwill allow us to do this though).TiagoDanin commentedon Jul 8, 2019
Name and version are already displayed in NP. And the output of
--dry-runis immediately displayed (no waiting),listronly show one line at a time.Another problem is that Yarn has no option
--dry-run.PS: Sorry for the delay.
itaisteinherz commentedon Jul 9, 2019
@TiagoDanin Since, as you said above, the output of the command isn't really helpful and the option doesn't exist for Yarn, let's just print the publish command.
cactyx commentedon Jul 15, 2019
Please also read through this issue about the
npm publishcommand.It's super important to know for sure where you are publishing to when it might be private stuff. A simple misconfiguration somewhere might lead to publishing to the NPM registry which you might not want.
issuehunt-oss commentedon Feb 22, 2020
@sindresorhus has rewarded $72.00 to @tiagodanin. See it on IssueHunt