Installed electron-abi of MacOS Catalina 10.15

~ -> npm install electron-abi -g
/usr/local/bin/electron-abi -> /usr/local/lib/node_modules/electron-abi/list-abi.sh
+ [email protected]
added 1 package from 1 contributor in 1.959s

tried to run but couldn't find any file

~ -> electron-abi
cp: TEMPLATE.md: No such file or directory
cat: versions.txt: No such file or directory
# electron-quick-start

... lines of README.MD ...

## License

[CC0 1.0 (Public Domain)](LICENSE.md)

It is missing from docs.

Electron's current version is1.7.5

Very helpful resource.

Can you add ABI and targets for Electron 1.6?

I recently needed this for a Windows Electron app but couldn't run it to get the ABI needed for a node module that required it for install.

When I run it, I get this:

digit@mighty-dev MINGW64 ~/Desktop/workspace/ (suhail/events)
$ electron-abi 
cp: cannot stat 'TEMPLATE.md': No such file or directory 
cat: versions.txt: No such file or directory 
## Getting started 

Please refer to the Electron [Quickstart](https://electronjs.org/docs/tutorial/first-app) first.

### Running Electron on Ubuntu

- sudo apt update
- sudo apt upgrade
- Install npm: sudo apt install npm & install npm via installer if you're on Windows 
- npm install
- sudo apt install typescript
- sudo apt install node-typescript
- sudo apt-get install -y libgtk2.0-0 libnotify-bin libgconf-2-4 libnss3 xvfb libxss1 libasound2
- cmd.exe: sudo npm install electron
- in bash: ./start.sh

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.