feat(cli, outdated): Adds 'Homepage' to outdated --long output. #81
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- `package.json`'s `homepage` property is displayed when using the `--long` option for `npm outdated`
zkat
approved these changes
Nov 13, 2018
- Adds `homepage` to `--parseable` output. - Updates `npm outdated --long` test to include `homepage` in expected output. - Adds `homepage` to `npm-outdated` documentation.
|
Great, thanks! I've made what I believe are the last few required changes:
Let me know if you think anything should be changed or updated! |
viladoit015
approved these changes
Nov 18, 2018
|
|
zkat
pushed a commit
that referenced
this pull request
Dec 10, 2018
* feat(cli, outdated): Adds 'Homepage' to outdated --long output. - `package.json`'s `homepage` property is displayed when using the `--long` option for `npm outdated` * test: npm outdated --long - Adds `homepage` to `--parseable` output. - Updates `npm outdated --long` test to include `homepage` in expected output. - Adds `homepage` to `npm-outdated` documentation. * fix: javascript standard style updates PR-URL: #81 Credit: @jbottigliero Reviewed-By: @zkat
This was referenced Oct 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 outdatedIt seems like the
npm outdatedutility 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
homepagewhen using the--longflag. I realize this is likely not the ideal solution (homepagemight 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 ofCHANGELOGfiles (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.TODOhomepagewhen use--parseablehomepagespecificnpm outdated --longtests.===
package.json'shomepageproperty is displayed when using the--longoption fornpm outdatedExample pretty" Output (generated from
npm/cli: