Vladi Bilonenko

Sorry for delay! On this problem: * if your instance is not supporting `HTTP HEAD` it's a problem; the tools relies on `HTTP HEAD`; is it possible for you to...

true, proxy is not supported.

Hi! I checked the address you mention `104.18.95.96` **EDIT:** I compared `traceroute registry.npmjs.org` with `traceroute 104.16.23.35` and its probably one of the addressed of `registry.npmjs.org` returned by their dynamic DNS...

@kennethchoe any chance you can fork it and play with timeout here https://github.com/delfrrr/npm-consider/blob/master/lib/getPackageDetails.js#L85 and here https://github.com/delfrrr/npm-consider/blob/master/lib/getPackageDetails.js#L107 Timeout can be set in `node-fetch` https://github.com/bitinn/node-fetch If it works, I will add the...

I tested ut a bit more and sometimes I would get ETIMEDOUT as well. I see two solutions: 1. quick one: decrease number of parallel requests (parallel threads in a...

@FlandersBurger if you just call `npm-consider install` you will see a menu where you can choose `Details`; is it what you need?

Hey @allenday please check the docs to build from source https://dekart.xyz/docs/contributing/build-from-source/

@allenday can you please confirm if `npm install` is completing/failing on your local? (see [steps](https://dekart.xyz/docs/contributing/build-from-source/)) Also can you please confirm which step fails in docker build? Please note that root...

hey @allenday ; I've launched VM instance on GCP and went through setup steps on it successfully using friend's GitHub token (to make sure there is no permission problem); System...

@allenday if you do experience problem, and build failed inside the docker I can only assume that problem is with your `.npmrc` file: * wrong path * wrong token let...