Features Videos Help About Updates
Menu Buy Now

JSLint

Basics
Getting Started
Refreshing Browsers
Browser Sync
Defaults For New Projects
Common Tasks
Set Language Options
Set Output Paths & Action
Build Your Project
Set Target Browsers
Critical Things
CodeKit + Git
Troubleshooting
License Recovery
Tools
Babel
Cache-Buster
Autoprefixer
Bower
Libsass
Bless
UglifyJS
Languages
Sass
Less
Stylus
JavaScript
CoffeeScript
TypeScript
Pug (Jade)
Haml
Slim
Kit
Markdown
JSON
Image Optimizers
SVG
PNG
JPEG
GIF
Frameworks
CodeKit Frameworks
Bourbon
Bourbon Neat
Bitters
Zurb Foundation
Google Web Starter Kit
Susy
Nib
Jeet
Compass
Syntax Checkers
ESLint
JSHint
JSLint
CoffeeLint
Advanced
Hooks
Adding Custom Languages
Team Workflows
Scripting CodeKit
Editor Plugins
Coda 2
Sublime Text
Atom
More
New in 3.0
Read-Only Mode
Upgrading From 2.0
FAQ
The JSLint logo

What's JSLint?

JSLint is the original JavaScript syntax checker.

This tool finds common errors in your JavaScript and enforces a coding style favored by its creator, Douglas Crockford, who literally wrote the book on JavaScript.


Advice: Use ESLint

While JSLint is the grandfather of all JavaScript syntax checkers, ESLint is what you should be using now. ESLint is far more configurable, checks for more issues, and has really easy-to-understand documentation. Most importantly, ESLint supports the newest JavaScript standards like ES6.

CodeKit 3.0 supports JSLint mostly for backwards-compatibility. As of 2016, ESLint is the industry standard in JavaScript syntax checkers. You should move to it immediately.

That said, this recommendation is in no way a condemnation of JSLint or Doug Crockford. It's just that the state-of-the-art has advanced since JSLint was created and modern JavaScript requires a more expansive syntax checker. Using JSLint today puts you at a disadvantage.


Using JSLint

Please see the help page for ESLint. Both tools are similar and the instructions for ESLint mostly apply to JSLint as well (though there are far fewer options for JSLint).


Made in San Diego, CA
Follow the Developer on Twitter

  • Email support
  • Found a bug?