Closed albert361 closed 11 months ago
I'm not sure. How's that normally handled with vanilla npm?
Typically, we can use either:
npm config set strict-ssl false
-> not good since it updates global .npmrc
npm config set cafile /path/to/cert.pem
-> not good since it updates global .npmrc
NODE_TLS_REJECT_UNAUTHORIZED=0 npm publish .....
npm publish --strict-ssl false .....
IMO we should at least have ability to use either 3 or 4 to let user temporary disable strict-ssl check ONLY for publishing..npmrc
is Okay, then it should be configured already.Gotcha. Opt 4 is definitely something I could add to the plugin, but for now I think you can use opt 3 by passing that env var to gradle
e.g. NODE_TLS_REJECT_UNAUTHORIZED=0 ./gradlew publish
@albert361 can you share where that --strict-ssl
option is documented? There's no mention of it in npm publish
cli command docs
@albert361 any comments or should I close this for now?
Closing tgis for now until someone can provide some npm documentation for this.
Hi,
Thanks for developing this plugin! Is there a way to bypass self-signed certificate error?