Algolia v4 JavaScript client strict TLS validation and custom CA bundle handling in Electron/React Native

Developers using Algolia's official JavaScript search client version 4 need to confirm whether the library honors custom certificate authority configurations when operating inside Electron or React Native wrappers. The v4 release enabled strict TLS verification by default and removed the previous fallback that tolerated self‑signed certificates, but the public API does not expose an option to inject a custom CA bundle.

Because the underlying HTTP layer relies on Node.js's https agent or the browser's fetch implementation, it is unclear if setting the NODE_EXTRA_CA_CERTS environment variable or adding roots to the platform's certificate store will be respected, leaving a gap in secure configuration for internal PKI or debugging proxy setups.

Does the Algolia v4 JavaScript client automatically pick up NODE_EXTRA_CA_CERTS in Node‑based environments? Does it trust custom roots added to the Electron or React Native certificate store when making HTTPS calls to the Algolia API?