You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running yarn install results in this error message: error Could not open cafile: ENOENT: no such file or directory, open '~/custom-certs.pem'
If you change the cafile directive to cafile=/users/kevin/custom-certs.pem then yarn install works fine.
What is the expected behavior?
Use of ~ in cafile should expand to the user's home directory. It should do the same expansion in other directives that accept file paths.
Please mention your node.js, yarn and operating system version.
node: v6.2.0
yarn: v0.21.3
The text was updated successfully, but these errors were encountered:
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
~ is not properly evaluated when used in the
cafile
directive in .npmrcIf the current behavior is a bug, please provide the steps to reproduce.
Consider the scenario of a private npm registry that uses a self-signed SSL certificate. A user's ~/.npmrc would look like this:
Running
yarn install
results in this error message:error Could not open cafile: ENOENT: no such file or directory, open '~/custom-certs.pem'
If you change the cafile directive to
cafile=/users/kevin/custom-certs.pem
thenyarn install
works fine.What is the expected behavior?
Use of ~ in cafile should expand to the user's home directory. It should do the same expansion in other directives that accept file paths.
Please mention your node.js, yarn and operating system version.
node: v6.2.0
yarn: v0.21.3
The text was updated successfully, but these errors were encountered: