Code quality tools
summary
JSHint fork of JSLint claims to stop being merely a checker by focusing on JavaScript/JSON only (HTML/CSS removed), uses a Pratt parser in its current engine, and ships a stable release that is already used by six companies in builds. It reports concrete plans: plugin hooks into the parse tree, per-option documentation linking to specs and blog posts, a style‑guide system for custom rules, and an experimental lexer rewrite to make extensibility practical.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:05Why am I doing this
- 2:13What are code quality tools
- 5:30JavaScript
- 7:33Python and Go
- 9:35Java
- 12:35JSON syntax checker
- 13:30JSON documentation
related talks
28mTreat test code as application code by linting
25mWrite Perfect Code with Standard and ESLint
25mBuilding High-Quality JavaScript Tools
14mGetting Started with JavaScript Linter | What Is Linter?
36mEnforcing coding standards in a JS library
31mCode Style and Violence
58mImproving the Quality of JavaScript Code
20mThey see me refactorin'. They hatin'