Response code 400 (Bad Request)

[weekens]

On attempt to run release with np, I get:

$ npx np

✖ Response code 400 (Bad Request)

I expect to at lease get information on what was actually wrong. Currently, there is no such information and no possibility to get verbose output.

Private Git repository. Private NPM registry.

[itaisteinherz]

Is the bash output you included the full output of np, or did you leave some things out? It would be helpful if you included the entire stacktrace.
Also, which npm, Node.js and Git versions are you using?

[weekens]

I've included the full np output, that's the point.

The versions are:

$ npm --version
6.8.0
$ nodejs --version
v11.10.0
$ git --version
git version 2.17.1

[itaisteinherz]

This seems like an issue with npx and npm, as even if np had a bug you would still see the initial version prompt logged out. Try the solutions proposed in this issue.
@sindresorhus Do you have an idea on why this happens?

[sindresorhus]

No idea. When using a private npm registry, you're on your own to figure things out as a lot of things could potentially break. I'm happy to merge in fixes, but I have no ability or interest in testing against private registries.

[weekens]

@sindresorhus , but how's about implementing a possibility to enable verbose output from np? This way I could try to figure out things myself, and this would be in general a good option.

[itaisteinherz]

Adding a --verbose option wouldn't help here since, as I said, the issue isn't with np.

[itaisteinherz]

@weekens I just noticed #317, which looks similar to the issue you're facing. Can you try using [email protected], which worked for @jdziat?

I think that main issue here and in #317 is that when using a private registry, np should check if the package name is available on the given registry instead of on npm. We could also just disable the name check altogether when publishing to a private registry.

[weekens]

@itaisteinherz , [email protected] works fine.

[sindresorhus]

@itaisteinherz npm-name should already support checking the name for private packages: sindresorhus/npm-name@c4e850b

[itaisteinherz]

@sindresorhus See sindresorhus/npm-name#31 (comment).