npm-why: add page #2784
Merged
npm-why: add page #2784
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
|
The build for this PR has failed with the following error(s): Please fix the error(s) and push again. |
|
LOL does a command like this even need a page? I mean, who installs this without knowing its one and only function? But well, I guess it's ok. |
mebeim
approved these changes
Feb 15, 2019
owenvoke
approved these changes
Feb 15, 2019
owenvoke
requested changes
Feb 15, 2019
Co-Authored-By: sbrl <[email protected]>
owenvoke
approved these changes
Feb 15, 2019
|
@sbrl ok fair enough, haha. Gotta love such simple commands 🤣 |
|
Absolutely! Check out #2213 for a list of commands we're currently working towards. |
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.
Another day, another page on my continuing quest to have a page for every command in my shell history :P