ExB SDK Setup Causing different Errors

TedCronin — Tue, 15 Feb 2022 21:53:50 GMT

So, I have started the process to configure the SDK, and I am seeing some errors.

npm WARN old lockfile FetchError: request to https://registry.npmjs.org/@babel%2fcore failed, reason: self-signed certificate in certificate chain
npm WARN old lockfile at ClientRequest.<anonymous> (D:\Program Files\nodejs\node_modules\npm\node_modules\minipass-fetch\lib\index.js:110:14)
npm WARN old lockfile at ClientRequest.emit (node:events:526:28)
npm WARN old lockfile at TLSSocket.socketErrorListener (node:_http_client:442:9)
npm WARN old lockfile at TLSSocket.emit (node:events:538:35)
npm WARN old lockfile at emitErrorNT (node:internal/streams/destroy:164:8)
npm WARN old lockfile at emitErrorCloseNT (node:internal/streams/destroy:129:3)
npm WARN old lockfile at processTicksAndRejections (node:internal/process/task_queues:83:21)
npm WARN old lockfile Could not fetch metadata for @babel/core@7.15.8 FetchError: request to https://registry.npmjs.org/@babel%2fcore failed, reason: self-signed certificate in certificate chain
npm WARN old lockfile at ClientRequest.<anonymous> (D:\Program Files\nodejs\node_modules\npm\node_modules\minipass-fetch\lib\index.js:110:14)
npm WARN old lockfile at ClientRequest.emit (node:events:526:28)
npm WARN old lockfile at TLSSocket.socketErrorListener (node:_http_client:442:9)
npm WARN old lockfile at TLSSocket.emit (node:events:538:35)
npm WARN old lockfile at emitErrorNT (node:internal/streams/destroy:164:8)
npm WARN old lockfile at emitErrorCloseNT (node:internal/streams/destroy:129:3)
npm WARN old lockfile at processTicksAndRejections (node:internal/process/task_queues:83:21) {
npm WARN old lockfile code: 'SELF_SIGNED_CERT_IN_CHAIN',
npm WARN old lockfile errno: 'SELF_SIGNED_CERT_IN_CHAIN',
npm WARN old lockfile type: 'system'
npm WARN old lockfile }
[#######...........] \ idealTree:inflate:@babel/generator: sill inflate node_modules/@babel/generator

So, this makes me think there may be a Firewall issue, however if I run...

npm config set strict-ssl false

I get further, but I still am seeing errors

npm ERR! code ERR_SOCKET_TIMEOUT
npm ERR! network Socket timeout
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.

Any Ideas? I am trying this on a Virtual Desktop on vxRails. I see no issues off network on my laptop, so definitely a internal IT issue.

Re: ExB SDK Setup Causing different Errors

jcarlson — Tue, 15 Feb 2022 22:23:13 GMT

I have not seen this error myself. Does the virtual machine have issues connecting with anything else? Can you try downloading the node cache and do an offline installation?

Also: if you think it would be a nice feature, please upvote my idea: https://community.esri.com/t5/arcgis-experience-builder-ideas/docker-images-for-experience-builder-developer/idi-p/1134383

Re: ExB SDK Setup Causing different Errors

TedCronin — Wed, 16 Feb 2022 23:02:49 GMT

Right now I am trying to get my Network Admin to add the https://registry.npmjs.org to the firewall. I looked at doing the offline install but chose not to go that way as I will be needing to install ExB on 15 other machines for other City Users and don't want to deal with extra headache as this is pretty basic to do off our network. One thing I could try is copy from my laptop and see if the node_modules will work as a copy to another onsite machine or if they have to be updated per machine.

topic Re: ExB SDK Setup Causing different Errors in ArcGIS Experience Builder Questions

ExB SDK Setup Causing different Errors

Re: ExB SDK Setup Causing different Errors

Re: ExB SDK Setup Causing different Errors