Skip to content
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

Log new versions as they are found #947

Open
3 tasks done
rethab opened this issue Sep 7, 2021 · 3 comments
Open
3 tasks done

Log new versions as they are found #947

rethab opened this issue Sep 7, 2021 · 3 comments

Comments

@rethab
Copy link

rethab commented Sep 7, 2021

  • I have searched for similar issues
  • 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 :)

@raineorshine
Copy link
Owner

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).

@raineorshine
Copy link
Owner

raineorshine commented Sep 7, 2021

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.

@lyswhut
Copy link
Contributor

lyswhut commented Nov 11, 2021

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

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants