feat(cli, outdated): Adds 'Homepage' to outdated --long output. #81
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My current workflow (which I assume is fairly common) is:
npm outdated
It seems like the
npm outdated
utility could provide a little more information to smooth out this process (and possibly enable some standardization around the changelog location).This change proposes the output of
homepage
when using the--long
flag. I realize this is likely not the ideal solution (homepage
might not always contain a changelog), but it seems like it would be a reasonable and helpful link to provide.I've been digging into
npm
's handling ofCHANGELOG
files (and it's permutations) to determine if there could be a more helpful link to provide here, but I haven't found anything that seems standardized or well documented.TODO
homepage
when use--parseable
homepage
specificnpm outdated --long
tests.===
package.json
'shomepage
property is displayed when using the--long
option fornpm outdated
Example pretty" Output (generated from
npm/cli
: