expo init on Windows 10 and self signed certificate in chain error

[acaland]

Hello,

I am struggling since the last 3 days to make expo init works on some Windows 10 machines.
I have read all around the web to fix the problem that is supposed to be related to proxy certificates. I have tried all the workarounds I found, even setting the CA of the proxy to NPM, but expo init continues to fails:

expo i prova2
√ Choose a template: » blank               a minimal app as clean as an empty canvas
request to https://registry.npmjs.org/expo-template-blank failed, reason: self signed certificate in certificate chain
FetchError: request to https://registry.npmjs.org/expo-template-blank failed, reason: self signed certificate in certificate chain
    at ClientRequest.<anonymous> (D:\Users\econtino\AppData\Roaming\nvm\v14.17.6\node_modules\expo-cli\node_modules\minipass-fetch\lib\index.js:110:14)
    at ClientRequest.emit (events.js:400:28)
    at TLSSocket.socketErrorListener (_http_client.js:475:9)
    at TLSSocket.emit (events.js:412:35)
    at emitErrorNT (internal/streams/destroy.js:106:8)
    at emitErrorCloseNT (internal/streams/destroy.js:74:3)
    at processTicksAndRejections (internal/process/task_queues.js:82:21)

So I tried to manually install the expo-template-blank with both npm and yarn and it will install without any issues. I even tried to use react-native-cli and I can confirm it works perfectly.

I don’t know what to try more. Any hints will be really appreciated.

Here the expo diagnostics:

  Expo CLI 4.11.0 environment info:
    System:
      OS: Windows 10 10.0.17763
    Binaries:
      Node: 14.17.6 - C:\Program Files\nodejs\node.EXE
      npm: 6.14.15 - C:\Program Files\nodejs\npm.CMD
    Expo Workflow: managed

Thank you

[acaland]

ok I think I have found the problem.
For some reason expo init doesn’t read the npm config variables, where I have set a custom CA file.
I had to set the NODE_EXTRA_CA_CERTS to the CA’s path directly and it worked.