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
Comments
This is also affecting |
Fixed in the 1.9.4, now available! Let me know if that fixes the issue for you 🙂 |
@arcanis the release notes for Could those please be updated to indicate that this issue has been addressed? |
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 🙂 |
@arcanis this gets past the original issue, however now |
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.
config set
to set a scoped registry by running either one of the following: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
nothttps://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)
The text was updated successfully, but these errors were encountered: