Add a JavaScript/TypeScript Linter to the DevHub Projects

[kj4ezj]

Following devrel issue 135, this issue has a JavaScript or TypeScript linter being added to each of the projects in this repo (three projects at the time of this writing), and being a required check on all builds.

The author recommends eslint with a linter configuration in the package.json similar to this. The eslint-config-airbnb-base is quite picky so there may be many rules that can and should be disabled. The author recommends restricting rules that cause a linter error (and thus a build failure) only to rules that possibly indicate a mistake. All other rules should be warnings or disabled. The only linter issues that should truly block a merge or a deployment should be linter issues that may genuinely indicate a mistake with repercussions.

See Also

• devrel issue 80 - Standup DevHub Infrastructure
• devrel issue 96 - DNS Mapping for learn.eosnetwork.com
• devrel issue 134 - Update DevHub Site
• devrel issue 135 - DevHub Frontend CICD
• devrel issue 137 - Encrypt DevHub Backend
• devhub issue 12 - Put AWS Resources into Terraform with a CICD Deployment
• devhub issue 13 - Document CICD System
• devhub issue 14 - Staging Environment
• devhub issue 15 - Backend CICD
• devhub issue 16 - Structures CICD
• devhub issue 17 - Add a JavaScript/TypeScript Linter to the DevHub Projects
• devhub issue 18 - Add BASH Linters for CICD Code
• devhub issue 19 - Include Test Suite in CICD