Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Locally installed np dependency failed on 'Verify user is authenticated' #256

Closed
artivilla opened this issue Apr 9, 2018 · 5 comments
Closed

Locally installed np dependency failed on 'Verify user is authenticated' #256

artivilla opened this issue Apr 9, 2018 · 5 comments

Comments

@artivilla
Copy link

It breaks on ✖ Verify user is authenticated but when I test npm whoami I get artivilla. I also have AddKeysToAgent yes in my ~/.ssh/config config file. Any other way I can I debug what might be causing this?

I've tried try ./node_modules/.bin/np or npx np which essentially both are accessing my local binaries.

Works when I run the command globally.

Current Setup: OSX Sierra 10.13.3
Current Versions: [email protected], [email protected], [email protected]
@jamsinclair
Copy link

Your local repository doesn't change the npm registry, via config or .npmrc, by chance?

I was having a similar problem when using locally with yarn. Yarn was supplying a different registry to npm which caused authentication to fail.

@artivilla
Copy link
Author

It's the default registry specified as registry.npmjs.org/:_authToken= with a token value. Nothing set in the local config either.

@artivilla artivilla reopened this Jun 21, 2018
@garytryan
Copy link

garytryan commented Jul 20, 2018 •
edited
Loading

I'm also having a similar problem.
If I run yarn np, I get a ✖ Verify user is authenticated message, when I test nom whoami I get my username back.

It works correctly if I run npx np

@jamsinclair
Copy link

jamsinclair commented Jul 23, 2018 •
edited
Loading

Finally I know why 🙌

See this issue yarnpkg/yarn#5683

@garytryan try yarn login and then run yarn np

I wonder if could be fixed in np, although perhaps more a yarn bug itself.

@garytryan
Copy link

@jamsinclair just got around to releasing a package. yarn login seems to do the trick

@itaisteinherz itaisteinherz mentioned this issue May 24, 2019
Closed
@brmscheiner brmscheiner mentioned this issue Jun 5, 2019
Open
@colinking colinking mentioned this issue Jun 18, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@artivilla @garytryan @jamsinclair