Skip to content

Login to private registry fails (Verdaccio, Nexus, …) #420

@kapooostin

Description

@kapooostin

Description

np fails to publish package due to login error:

? This scoped repo @scope/pkg hasn't been published. Do you want to publish it publicly? Yes

  ❯ Prerequisite check
    ↓ Ping npm registry [skipped]
    ✔ Check npm version
    ✔ Check yarn version
    ✖ Verify user is authenticated
      → You must be logged in. Use `npm login` and try again.

Yet I did login beforehand and both npm publish and yarn publish succeeded without any hitch. np also fails to ensure that my repo has been published because it has been more than once.

Steps to reproduce

I'm trying to publish a scoped package to Gemfury.io.

Expected behavior

np should use credentials npm and yarn use to login to my custom registry.

Environment

Node.js - 10.15.3 (via n)
npm - 6.9.0
yarn - 1.16.0
Git - 2.21.0
OS - OSX 10.14.4

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions