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.

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

1.9.2: Scoped Registries are being ignored #6174

Closed
clintwood opened this issue Jul 29, 2018 · 5 comments · Fixed by #6207
Closed

1.9.2: Scoped Registries are being ignored #6174

clintwood opened this issue Jul 29, 2018 · 5 comments · Fixed by #6207
Assignees
Labels

Comments

@clintwood
Copy link
Contributor

clintwood commented Jul 29, 2018

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

Bug

What is the current behavior?

EDIT: This seems limited to yarn global ...

Since a recent (via my distro) update to yarn 1.9.2, scoped registry config set in .yarnrc or .npmrc are no longer being respected/used.

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

  1. Use config set to set a scoped registry by running either one of the following:
$ npm config set @myscope:registry http://my.private.registry.com
# or
$ yarn config set @myscope:registry http://my.private.registry.com
  1. Try adding a package from your scoped registry:
$ yarn global add @myscope/my-private-package
  1. You'll get an error message that says:
    error An unexpected error occurred: "https://registry.yarnpkg.com/@myscope%2fmy-private-package: Not found".

What is the expected behavior?

It should install the package from your private registry set for the scoped package. In this example it should use http://my.private.registry.com not https://registry.yarnpkg.com.

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

node: 10.7.0
yarn: 1.9.2
Elementary OS Loki (Ubuntu 16.04)

@fenduru
Copy link
Contributor

fenduru commented Jul 30, 2018

This is also affecting yarn create

@arcanis
Copy link
Member

arcanis commented Aug 3, 2018

Fixed in the 1.9.4, now available! Let me know if that fixes the issue for you 🙂

@hutson
Copy link

hutson commented Aug 8, 2018

@arcanis the release notes for 1.9.4 do not indicate any changes to the package manager - https://github.com/yarnpkg/yarn/releases/tag/v1.9.4

Could those please be updated to indicate that this issue has been addressed?

@arcanis
Copy link
Member

arcanis commented Aug 8, 2018

As mentioned in the release notes for the 1.9.4, it's only been released because of our release process. Please refer to the release notes for the 1.9.3 for the actual changes 🙂

https://github.com/yarnpkg/yarn/releases/tag/v1.9.3

@fenduru
Copy link
Contributor

fenduru commented Aug 10, 2018

@arcanis this gets past the original issue, however now yarn create @scope/package fails as it attempts to execute C:\Users\me\AppData\Local\Yarn\bin\@scope\package however the binary got installed to AppData\Local\Yarn\bin\package

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

Successfully merging a pull request may close this issue.

5 participants