Ignore check for npm name when --no-publish

[piuccio]

I'm using np for a private package that is not published on npm but on a separate server using the command

np --yolo --no-publish

and recently after updating I started getting these messages

? This scoped repo @private/package hasn't been published. Do you want to publish it publicly? (Y/n)

It freaked me out at first but looking at the code it seems like it's supposed to prevent people from publishing a scoped package publicly on npm, which is fine, but since I'm using --no-publish I don't expect the package to be published anyway.

So either there's something wrong and np is trying to publish even if --no-publish is set or that check should be ignored if we're skipping publishing

yaodingyd earned $20.00 by resolving this issue!

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on Issuehunt to raise funds.

[sindresorhus]

Yeah, that task should be skipped when --no-publish is passed.

[IssueHuntBot]

@issuehuntfest has funded $20.00 to this issue. See it on IssueHunt

[sindresorhus]

@yaodingyd You need to submit your PR URL in IssueHunt to get the reward for this.

[IssueHuntBot]

@yaodingyd has submitted a pull request. See it on IssueHunt

[yaodingyd]

@sindresorhus thanks!

[IssueHuntBot]

@sindresorhus has rewarded $18.00 to @yaodingyd. See it on IssueHunt

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