search

rogeriochaves / npm-force-resolutions

Force npm to install a specific transitive dependency version
567 stars 28 forks source link

Updated timeout to 60000 #34

Open bilalbaqar opened 3 years ago

bilalbaqar commented 3 years ago

Updated timeout to 60000 from 8000ms. Issue https://github.com/rogeriochaves/npm-force-resolutions/issues/33

bwhite94 commented 2 years ago

This would likely fix Issue #49 as well. The only other option would be to make this configurable.

ewrayjohnson commented 2 years ago

I have a colleague who is experiencing this problem while others on our team are not. Downgrading works, but is insufficient as other newer features are also disabled. Any estimate on when this will get merged? How can we get a version without building it ourselves. We don't want to have to install Clojure.

ewrayjohnson commented 2 years ago

It turns out that my colleague's npm registry was somehow set to an obscure mirror. I guess the mirror was slow. Setting the npm registry to the default fixed it (https://registry.npmjs.org/). Here is the command: npm config set registry https://registry.npmjs.org/