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 >= 14.14
Hi, i want to ask if there is a way to log package-manager logs or progress bar after running install script?
also i think i'm facing an issue with jsonUpgraded it doesn't log updated dependencies after process complete (it was logging in earlier version) so i'm not sure if its a bug or i'm missing something.
Hi, i want to ask if there is a way to log package-manager logs or progress bar after running install script?
Yes, that's a good idea. I have added this as the default behavior in v16.14.4.
also i think i'm facing an issue with jsonUpgraded it doesn't log updated dependencies after process complete (it was logging in earlier version) so i'm not sure if its a bug or i'm missing something.
The format: lines options is rather special: It cannot be combined with jsonUpgraded or other format options. So if you pick one or the other it should work fine. I will add better error messaging for conflicting options.
For future reference, please create separate issues for separate points of inquiry, regardless of how small they are. That will help me track conversations and progress independently.
npm-check-updates
node >= 14.14
Hi, i want to ask if there is a way to log package-manager logs or progress bar after running install script?
also i think i'm facing an issue with jsonUpgraded it doesn't log updated dependencies after process complete (it was logging in earlier version) so i'm not sure if its a bug or i'm missing something.
Thanks for this amazing work
.ncurc:
Current Behavior
jsonUpgraded Doesn't log updated dependencies after complete (it was logging in earlier version)
process of ncu command with the specified config above
Expected Behavior
Output updated dependencies
The text was updated successfully, but these errors were encountered: