Skip to content

Cannot install any packages starting with '@' #6730

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.

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

Closed
markpradhan opened this issue Nov 28, 2018 · 3 comments
Closed

Cannot install any packages starting with '@' #6730

markpradhan opened this issue Nov 28, 2018 · 3 comments
Assignees
Labels

Comments

@markpradhan
Copy link

markpradhan commented Nov 28, 2018

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
Cant install any packages starting with '@'

If the current behavior is a bug, please provide the steps to reproduce.
yarn install or yarn

yarn install v1.12.3
info No lockfile found.
[1/4] 🔍  Resolving packages...
error Couldn't find package "@sentry/browser" on the "npm" registry.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

What is the expected behavior?
Simply install the packages

Please mention your node.js, yarn and operating system version.
Tried node 8.x 9.x 10.x, yarn 1.12.3, macOS 10.14.1

I tried removing yarn.lock, changing registry to npm.
yarn add @... doesn't work either.

Looks like others have issues upgrading as well:
#6727

Did some more testing:
yarn add uuid -> works
yarn add @sentry/browser -> fails

Npm seems affected as well:
npm install uuid -> works
npm install @sentry/browser ->

npm ERR! code E401
npm ERR! 401 Unauthorized: @sentry/[email protected]

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/mark/.npm/_logs/2018-11-28T11_43_45_028Z-debug.log
@ghost ghost assigned kaylie-alexa Nov 28, 2018
@ghost ghost added the triaged label Nov 28, 2018
@arcanis
Copy link
Member

arcanis commented Nov 28, 2018

Thanks for the report - merging it with #6727.

It seems to be a problem on npm's side:
https://npm.community/t/can-t-install-scoped-packages-e401-unauthorized/3631

@arcanis arcanis closed this as completed Nov 28, 2018
@mtarapata
Copy link

Hi All,
In my case it helped when I deleted line with authToken from my .npmrc
progress=true
//registry.npmjs.org/:_authToken=xxxxxxxxxxxxxxxxxxx <-delete this

@nothingismagick
Copy link

Yes, this seems to be consensus:
#6312 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants