-
Notifications
You must be signed in to change notification settings - Fork 199
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
Add which command using npm module which #71
Conversation
I vetted the source code of the |
Haven't tested this yet, but I'm in favor of re-using existing modules if they're robust enough. @khuongduybui does this also support things like: $ export foo="cat"
$ which $foo # outputs path to cat If so, could you add tests to the pre parser test file? |
const results = cash.which('cmd'); | ||
console.log(typeof results); | ||
results.should.not.equal(''); | ||
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should be pretty easy tests for basic functionality. Not trying to re-handle all of the tests that the lib already provides, but a basic test or two that verifies the author didn't butcher the package on the latest update would be good.
Hey looks great, thanks!!! Added some notes. After this, should be good to merge! |
What does this return in the case of I could see a user being confused about why |
Should probably just do the system one - if Cash is installed on Windows globally, it will return the Cash one anyway. |
Yeah, I'd agree it's probably the better route (I personally hate the |
@dthree: ready for merge |
Thanks! Will do final review shortly. |
Add which command using npm module which
👍 sorry for the delay |
No description provided.