Np: Locally installed `np` dependency failed on 'Verify user is authenticated'

[artivilla]

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]

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]

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

[garytryan]

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]

Finally I know why 🙌

See this issue https://github.com/yarnpkg/yarn/issues/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]

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