yarn 1.0.1 doesn't use custom registry from .npmrc

Created on 12 Sep 2017 · 11Comments · Source: yarnpkg/yarn

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

What is the current behavior?
When having a custom registry in .npmrc, yarn doesn't use it and keep using the default npm registry instead. This results in errors during install with:

error Couldn't find package "aaa" on the "npm" registry.

If the current behavior is a bug, please provide the steps to reproduce.
Create a npmrc file with a custom registry:

registry = https://another-registry.com

Then try to install your dependencies from the custom registry

What is the expected behavior?
It worked fine with v0.x. The custom registry was used when fetching the dependencies.

Please mention your node.js, yarn and operating system version.
Node 8.4.0
Yarn 1.0.1
Mac OS Sierra

cat-bug cat-documentation

Source

tleunen

👍5

Most helpful comment

Please, release it ;)

Noo, I'm saving it for myself :P

BYK on 13 Sep 2017

😄5

All 11 comments

The error message is misleading since it just uses the registry id but uses the URL provided underneath. I think you are experiencing an issue that is fixed on master. Would you mind trying one of the nightlies?

BYK on 12 Sep 2017

I'll use this issue to make the error message more accurate if your issue is resolved on master. Thanks for reporting!

BYK on 12 Sep 2017

Indeed, it worked with the latest nightly.
Do you know when a new version of yarn with this fix will be released?

Thank you.

tleunen on 12 Sep 2017

Do you know when a new version of yarn with this fix will be released?

We are getting ready for it as we speak. It should be out in a few days.

Thanks for verifying!

BYK on 12 Sep 2017

Oh wait, I need to keep this open to fix the error message :)

BYK on 12 Sep 2017

I think you are experiencing an issue that is fixed on master. Would you mind trying one of the nightlies?

@BYK Could you point me to this issue? I think we're experiencing it on 1.0.1. Yarn doesn't seem to be finding (getting a 404) private modules resolved on the npmjs registry. I want to see if ya'll have resolved it already.