Closed MadaraUchiha closed 3 years ago
Installing npm-force-resolutions@0.0.3
as a devDependency makes it all work again.
that should have been fixed in 0.0.5 (check #22), weird that you are still getting it. Can you try to run npx npm-force-resolutions@0.0.5
just to make sure?
I am getting that version 0.0.5 does not exist. Although that one might be attributed to my org's artifactory/mirror.
I've confirmed that setting the registry back to the public npm one resolves this issue. I'll hash this out with our org's artifactory keepers.
Cheers!
If I use 0.0.5, I still get the same issue:
Error: Timeout trying to fetch resolutions from npm
If I force it to use 0.0.3, it works fine
@jurgensweere That appears to be a different issue, probably best to open a new one :)
@jurgensweere this is probably related to 0.0.5 not handling private registries properly, 0.0.6 should have that fixed, please follow on #26
Running
npx npm-force-resolutions
always fails, whether it's in dev dependencies or not, whether I have resolutions or not, whether I have dependencies at all or not.OS: Mac Node version: 12.13.1
Example package.json (default
npm init
+ preinstall script):npm i
output:The mentioned debug.log: