This week I used ESlint to resolve over 150 issues in a game I created, GeoAsteroids. You can see the work in this PR. I also use a pre-commit hook to lint and format code pushing to remote. All I had to do was install a tool called Husky, and add a pre-commit file in the .github folder. pre-commit runs:
npm run lint-fixwhich is defined in my package.json file,
// package.json
"scripts": {
...
"lint": "eslint . --ext .js,.ts",
"lint-fix": "eslint . --fix --ext .js,.ts",
},lint-fix is run in the pre-commit hook and lint is run during the CI build process with Git Actions. This way, I fix the issues locally before the code is committed, and it's rechecked before it makes it into a remote branch.
Add a linter to your codebase today!
Comments
- No comments yet.

John Solly
A hands-on AI practitioner who transitioned to a CTO role to broaden my impact.
Most of my career has been dedicated to developing spatial systems at Esri, startups, and federal agencies. Currently, I lead technology strategy for Leidos' Health IT division, supporting agencies such as SSA, VA, and HHS.
My primary focus is the convergence of spatial computing and AI, enabling machines to interpret the physical world and applying these capabilities to meaningful missions.
Please reach out if you are interested in spatial systems or advancing AI within the federal government.




0