Ignore check for npm name when `--no-publish` #319

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