You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the latest version of npm-check-updates
I am using node >= 10.17
It would be nice if new versions of packages would be printed out as they are found. I have tried silly mode, but even then I can only see new versions once the entire process was successful.
Background: For better or worse, I'm am using a not only slow but also unstable registry. This means ncu -u often times out (even when increasing the timeout by 10x) or fails for some other reason late in the process. This means I don't have any new versions at all even though ncu made 90% progress.
By printing new versions as they are discovered, I could at least fix some of the dependencies manually :)
The text was updated successfully, but these errors were encountered:
I agree! That would be a better user experience. It involves some structural changes to the package fetching pipeline. I think it would be a good idea to tackle this after the conversion to typescript (#888).
There is the annoying point that the cli columns won't line up if they are output individually. I think the cli will need to re-render the whole table each time a new version is retrieved.
My network connection official npm registry is unstable,
A large number of requests sent by ncu -u occasionally have some connection failures, causing ncu to stop working, so adding connection failure retries can help alleviate this problem.
same: #959
npm-check-updates
node >= 10.17
It would be nice if new versions of packages would be printed out as they are found. I have tried
silly
mode, but even then I can only see new versions once the entire process was successful.Background: For better or worse, I'm am using a not only slow but also unstable registry. This means
ncu -u
often times out (even when increasing the timeout by 10x) or fails for some other reason late in the process. This means I don't have any new versions at all even though ncu made 90% progress.By printing new versions as they are discovered, I could at least fix some of the dependencies manually :)
The text was updated successfully, but these errors were encountered: