cafile or who .npmrc ignored

[andypillip]

Hei there.

We are using our own registry, which requires our own CA and intermediate certificates. That's why we configure our own registry and cafile in .npmrc.

I can run npm info <mypackage> and yarn info <mypackage> without issues, but if I run yarn-check, every package is giving the following error:

Registry error unable to verify the first certificate

I verified with --verbose if npm is actually using our registry, and it's alright.

yarn-check --debug doesn't give me any hint on the used registry. I'm concluding the tool is either ignoring .npmrc altogether, or the ̀ cafile`.

[yhnavein]

Have you checked if it works in the npm-check ?

[CTimmerman]

Why would an alternative to npm use .npmrc? Try making a .yarnrc.

[andypillip]

Well as far as I remember, in a minimal config mindset, you can use .npmrc with yarn. If that's the case, the config file should be respected in it's entirety, otherwise that feature is broken.

I'm sorry to not being able to reproduce or help resolving the issue, I don't work on that project any more.