New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: minTimeout is greater than maxTimeout #1155
Comments
Hi, thanks for reporting. That's very strange. I am also on OSX 12.4 (m1 chip) and I didn't get this error with the exact same node, npm, and ncu versions. I looked at the code and the only thing I noticed related to timeouts is that I removed Otherwise, it is likely a dependency bug. |
Hey Raine, sorry for any inconvenience, I just analyzed the source code of the ncu (the files that were throwing the error) and found that the error was in my settings, specifically in |
same issue here
|
@chungmarcoo Please post your npm config (tokens elided) and the result of |
|
@chungmarcoo And your npm config please? |
|
@chungmarcoo Thank you. I was able to reproduce the issue, and found that libnpmconfig does not parse the types of config values. So Fixed and published in |
Happy to hear your update. I will try the update tomorrow, appreciate for your work and have a good day. |
npm-check-updates
node >= 14
I'm using the node 18.4.0, ncu 15.0.1, npm 8.12.1, macOs Monterey 12.4 (m1 chip).
Steps to Reproduce
ncu
Current Behavior
After updating to version 15.0.1, this error appeared.
The text was updated successfully, but these errors were encountered: