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

yarn fails to install public scoped packages #1260

Closed
Offirmo opened this issue Oct 19, 2016 · 4 comments
Closed

yarn fails to install public scoped packages #1260

Offirmo opened this issue Oct 19, 2016 · 4 comments

Comments

@Offirmo
Copy link

Offirmo commented Oct 19, 2016 •
edited
Loading

Related but not exactly the same as #825, and most likely related to #991, #1234

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

What is the current behavior?
Trying to install a free, scoped package

yarn add --dev @offirmo/cli-toolbox
yarn add v0.16.0
[1/4] Resolving packages...
error Couldn't find package "@offirmo/cli-toolbox" on the "npm" registry.

However, this fine module is public and available on npm https://www.npmjs.com/package/@offirmo/cli-toolbox

What is the expected behavior?
It should find the module in the npm registry and install it

Please mention your node.js, yarn and operating system version.

  • node 6.9.0
  • yarn 0.16.0
  • Ubuntu 16.04 latest
@Offirmo Offirmo changed the title yarn fail to install a public scoped package yarn fails to install a public scoped package Oct 19, 2016
@Offirmo Offirmo changed the title yarn fails to install a public scoped package yarn fails to install public scoped packages Oct 19, 2016
@Offirmo
Copy link
Author

Offirmo commented Oct 19, 2016

Thanks for yarn, this tool is very promising !

@hawkrives hawkrives mentioned this issue Oct 19, 2016
Closed
@jsynowiec
Copy link
Contributor

jsynowiec commented Oct 19, 2016 •
edited
Loading

Are you using any private registry, http/https proxy or something similar? I've just successfully installed this package.

$ yarn add --dev @offirmo/cli-toolbox
yarn add v0.16.0
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 📃  Building fresh packages...
success Saved lockfile.
success Saved 233 new dependencies.
├─ @offirmo/[email protected]
├─ [email protected]
(...)

@Offirmo
Copy link
Author

Offirmo commented Oct 20, 2016

@jsynowiec I'm indeed accessing npm through my company's npm proxy.

I'll disable it and recheck.

@Offirmo
Copy link
Author

Offirmo commented Oct 21, 2016

@jsynowiec confirmed: removing the npm proxy solves the error.

I'll report it to the proxy maker.

Sorry for the trouble.

@Offirmo Offirmo closed this as completed Oct 21, 2016
vbfox added a commit to vbfox/yarn that referenced this issue Oct 21, 2016
@vbfox
Don't let an authorization be empty
21174ce 
It create problems with some servers like ProGet when used as a nuget
cache.

It's most likely the source of yarnpkg#825 and yarnpkg#1260
@vbfox vbfox mentioned this issue Oct 22, 2016
Merged
vbfox added a commit to vbfox/yarn that referenced this issue Oct 22, 2016
@vbfox
Don't let an authorization be empty
aae4041 
It create problems with some servers like ProGet when used as a nuget
cache.

It's most likely the source of yarnpkg#825 and yarnpkg#1260
vbfox added a commit to vbfox/yarn that referenced this issue Oct 24, 2016
@vbfox
Don't let an authorization be empty
0901ab4 
It create problems with some servers like ProGet when used as a nuget
cache.

It's most likely the source of yarnpkg#825 and yarnpkg#1260
sebmck pushed a commit that referenced this issue Oct 25, 2016
@vbfox
Don't let the authorization header be empty (#1373)
716503f 
* Don't let an authorization be empty

It create problems with some servers like ProGet when used as a nuget
cache.

It's most likely the source of #825 and #1260

* Fix flowtype checks

* Revert the change to the type returned by getAuth
@anp anp mentioned this issue Mar 30, 2017
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
2 participants
@Offirmo @jsynowiec