Go to file
Kunal Dabir 1ad2f05548 its possible because of many more 2018-11-15 10:44:33 +05:30
.editorconfig release 1.0 2017-08-29 12:01:11 +05:30
.gitattributes adding usual suspects for project root 2015-02-12 19:28:24 +05:30
.gitignore adding usual suspects for project root 2015-02-12 19:28:24 +05:30
.hastest.bats added: colors (#26) 2018-11-15 10:39:17 +05:30
.travis.yml release 1.0 2017-08-29 12:01:11 +05:30
LICENSE its possible because of many more 2018-11-15 10:44:33 +05:30
Makefile release 1.0 2017-08-29 12:01:11 +05:30
README.md link svg 2018-04-08 22:33:10 +05:30
demo.svg add demo svg 2018-04-08 22:29:36 +05:30
has added: colors (#26) 2018-11-15 10:39:17 +05:30

README.md

has

has checks presence of various command line tools on the path and also reports their installed version

Build Status Open Source Helpers

demo

How ?

Download the has file. There is no dependency apart from bash itself

$ has node npm java git gradle 
✔ node 8.2.1
✔ npm 5.3.0
✔ java 1.8.0
✔ git 2.14.1
✔ gradle 4.0.1

If everything is good has exits with status code 0. The status code reflects number of commands not found on your path.

$ has node go javac
✔ node 8.2.1
✔ go 1.8.3
✘ javac

And echo the status:

$ echo $?
1

Installing

Just download the has script in your path.

git clone https://github.com/kdabir/has.git && cd has && make install

If you are lazy, you can run has directly off the internet as well:

curl -sL https://git.io/_has | bash -s git node npm
✔ git 2.14.1
✔ node 8.2.1
✔ npm 5.3.0

And if that's too much of typing every time, setup an alias

alias has="curl -sL https://git.io/_has | bash -s"

And use it

$ has git
✔ git 2.14.1

command not understood by has?

Let's say $ has foobar returns foobar not understood, because has may not have whitelisted foobar.

In such cases, pass HAS_ALLOW_UNSAFE=y has foobar. This is should still check for existance of foobar and tries to detect version as well.

Demo

asciicast

Contributing

Build Status

  1. Star the repo, tweet about it, spread the word
  2. Update the documentation (i.e. the README file)
  3. Adding support for more commands
  4. Adding more features to has