Lint Javascript code

[ericanaughton]

Suggested by @whazzmaster: Use eslint or similar; hook it up to travis or circleci so we can get style feedback before commit/PR merge.

In order to maintain standards and consistency As a developer working on LMHT I want to have a linter give me feedback before I get my PR reviewed.

Acceptance Criteria

• There is a set of rules that scans all of the javascript files to make sure that the code is consistent, and clean.
• All users can run the linter to verify that they don't have errors.
• npm install should install everything needed to be able to run the linter
• npm test should run the linter with the needed arguments
• node_modules directory should not be commit to github
• Github shows the build as failing if the linter has errors.
• Readme is updated to explain how to install and run the linter

[ericanaughton]

@bigtiger should we use TravisCI or CircleCI?

[ericanaughton]

PR https://github.com/adorableio/LMHT/pull/36 ready to reviews (adds linter)

PR https://github.com/adorableio/LMHT/pull/35 appeases the linter errors (rules are set at a basic level for now). This will not be ready to merge until the previous PR is merged and a PR with TravisCI is merged.

[ericanaughton]

linter and travis ci is merged, fixes are ready for review https://github.com/adorableio/LMHT/pull/35

[ericanaughton]

merged