Related: #249/#250 -no-git-tag-version is 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

One thing you could do at the moment to achieve this is to avoid setting an upstream branch, which would make np skip pushing to the remote (however this is obviously a hack, not a solution).
Note that this is also related to #386.

Adding a dry run option does sound interesting and useful, though. We could add a --preview flag which only prints out the changes/actions np is going to make without actually doing those.

@IssueHunt has funded $80.00 to this issue.

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.

I just noticed the --dry-run flag for npm publish, which could be useful here.

I just noticed the --dry-run flag for npm publish, which could be useful here.

I don't understand 🤔. Did you mean: --no-publish ?

No, this is what I meant:

I believe not, because the NP does not show output of NPM.

I believe not, because the NP does not show output of NPM.

Maybe we could show parts of the output returned by npm publish --dry-run, or even the whole output (I'm not sure if listr will allow us to do this though).

Name and version are already displayed in NP. And the output of --dry-run is immediately displayed (no waiting), listr only show one line at a time.

Another problem is that Yarn has no option --dry-run.

PS: Sorry for the delay.

@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.

Please also read through this issue about the npm publish command.

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.

@sindresorhus has rewarded $72.00 to @tiagodanin. See it on IssueHunt

• 💰 Total deposit: $80.00
• 🎉 Repository reward(0%): $0.00
• 🔧 Service fee(10%): $8.00