package.json, license, linter fixes

[ungoldman]

Hi @timwis!

Cool project! I added a couple things and fixed a couple things, feel free to merge or toss this out if you don't agree as some of the package.json fixes are a bit prescriptive.

• I added a LICENSE file and linked to it from your README.md.
• I fixed two no-unused-vars errors in tests/ that were causing the linter to fail.
• I removed relative links to ./node_modules/ binaries in scripts (npm will pick these up for you, so you can just write it as "lint": "standard --verbose | snazzy", instead of "lint": "./node_modules/standard/bin/cmd.js --verbose | ./node_modules/snazzy/bin/cmd.js",.
• I ran fixpack, a handy utility for organizing and linting package.json files, and added some missing properties (bugs, homepage, keywords, repository).
• I changed the server script to start, so you can just run npm start instead of npm run server now. start and test are the two standard script commands that npm will recognize for free (so you can run npm start and npm test instead of npm run ... -- less typing! yay) start is also the default command cloud deployment services like heroku will look for.
• I fixed the main property in package.json which was pointing to a non-existent index.js file.

[timwis]

Wow Nate, this is awesome - thank you! Definitely learnt something here - especially on item 3 - that will save me a lot of time trying to hunt down the binaries. I didn't realize node figured that out for non global packages. Thanks!

[ungoldman]

@timwis yep, anything that is installed in node_modules and has a bin property in its package.json will be symlinked into node_modules/.bin and accessible by npm scripts. I also add ./node_modules/.bin to my path so I can run commands in node projects using the project-specific binaries (example). Glad I was able to contribute :)