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

fix: let fetch option respect NODE_TLS_REJECT_UNAUTHORIZED env as def… #257

Closed
wants to merge 1 commit into from

Conversation

casyalex
Copy link

node-gyp call this request by default and, strictSSL always be true. And NODE_TLS_REJECT_UNAUTHORIZED can't effect this variable.

See this issue

@wraithgar
Copy link
Member

Is there something preventing you from setting strict-ssl=false in your .npmrc file?

@wraithgar
Copy link
Member

The change for this would need to happen in the npm config for strict-ssl itself. It would also be a breaking change so it would need to be added to the npm 11 roadmap (npm 10 roadmap has already been locked in and shipping this month).

@wraithgar
Copy link
Member

I added this to the considerations for npm 11

@casyalex
Copy link
Author

casyalex commented Jul 20, 2023

Is there something preventing you from setting strict-ssl=false in your .npmrc file?

The error happened in post-install stage, when some package need node-gyp compile after install, so i am guessing the npm config or yarn config won't take effect.

I did try using set npm config, it did not work.

@jbgomond
Copy link

Also having the issue. Do you have some news here ? It's blocking all downloads behind a corporate proxy :(

Thanks

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

Successfully merging this pull request may close these issues.

None yet

3 participants