Cannot exec `npm install`

[mishina2228]

I could not execute npm install on my local environment and also on GitHub Actions.

https://github.com/mishina2228/mocha-headless-chrome/runs/6862661629?check_suite_focus=true

npm ERR! code ETIMEDOUT
npm ERR! syscall connect
npm ERR! errno ETIMEDOUT
npm ERR! network request to https://repo.br.hmheng.io/artifactory/api/npm/npm-remote/yocto-queue/-/yocto-queue-0.1.0.tgz failed, reason: connect ETIMEDOUT 10.35.19.146:443
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.
npm ERR! network 
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/runner/.npm/_logs/2022-06-13T13_52_15_594Z-debug-0.log

https://github.com/direct-adv-interfaces/mocha-headless-chrome/blob/6c95d3729cbbbb1ca0e5f017885f82c57b5b0657/package-lock.json#L1738-L1746

It seems that repo.br.hmheng.io is not available.

Can we recreate package-lock.json?

[mishina2228]

Looks like package-lock.json is updated in #61. Hi @drochgenius, we cannot access to repo.br.hmheng.io at the momement, do you have any information?

[drochgenius]

Hi @mishina2228 ,

Sorry, I'm using a custom NPM registry mirror, and looks like I mistakenly commited an lockfile with entries pointing to this mirror. I've just opened a PR to fix the lockfile here: #64

In the meantime, you can simply delete your local package-lock.json and run npm install to regenerate a new update one.

Hope it helps

[mishina2228]

That makes sense! This is the first time I have learned about custom NPM registry.

Thanks for opening the PR! I will close this issue when it is merged.