eslint vs jshint vs standard vs jscs

JavaScript Code Quality and Style Enforcement Tools

eslint, jscs, jshint, and standard are all tools designed to improve JavaScript code quality by identifying problematic patterns, enforcing coding conventions, and preventing common errors. They operate as static analysis linters that parse source code without executing it, offering feedback on syntax, style, and potential bugs. While they share the same broad goal, they differ significantly in architecture, configurability, rule philosophy, and current maintenance status.

Package	Downloads	Stars	Size	Issues	Publish	License

eslint	81,817,162	26,893	2.89 MB	93	7 days ago	MIT
jshint	666,192	9,069	3.31 MB	461	-	MIT
standard	530,829	29,427	164 kB	128	a year ago	MIT
jscs	86,394	4,953	-	0	10 years ago	MIT

JavaScript Linters Compared: ESLint, JSCS, JSHint, and Standard

Choosing the right JavaScript linter impacts code consistency, bug prevention, and team productivity. While all four tools aim to improve code quality, their approaches, capabilities, and current viability vary dramatically. Let’s examine them through real engineering lenses.

⚠️ Maintenance Status: Is It Still Alive?

jscs is officially deprecated — its GitHub repository states: "JSCS is not maintained anymore. Please consider migrating to ESLint." The npm page confirms this with a deprecation notice. Do not use it in new projects.

jshint, while still published, has seen minimal updates in recent years and lacks support for many modern JavaScript features without workarounds.

standard and eslint are both actively maintained, with regular releases and strong community adoption.

💡 Rule of thumb: If a tool isn’t actively maintained, it will fall behind evolving JavaScript standards — leading to false positives, missed errors, or incompatibility with newer syntax.

🔧 Configuration Philosophy: Flexible vs Opinionated

eslint is fully configurable. You define every rule or extend shared configs (like eslint-config-airbnb).

// .eslintrc.js
module.exports = {
  env: { es2021: true },
  extends: ['eslint:recommended'],
  rules: {
    'no-var': 'error',
    'prefer-const': 'warn'
  }
};

standard has no configuration file. All rules are baked in. To override, you must use inline comments or switch tools.

// No .standardrc or config file exists
// This code passes Standard:
const greet = name => console.log('Hi', name)
// Note: no semicolon, single quotes, 2-space indent

jshint uses a .jshintrc JSON file, but options are limited to built-in rules.

// .jshintrc
{
  "esversion": 6,
  "strict": true,
  "undef": true
}

jscs (deprecated) used a config file similar to JSHint but focused solely on style (not code correctness).

// .jscsrc (historical example)
{
  "validateIndentation": 2,
  "requireSemicolons": true
}

🛠️ Modern JavaScript Support

eslint supports ES2020+ natively and can parse JSX, TypeScript, and experimental syntax via parsers like @babel/eslint-parser or @typescript-eslint/parser.

// ESLint handles modern code out of the box
const users = await fetch('/api/users').then(r => r.json())
const jsx = <div>Hello {users[0]?.name}</div>

jshint requires explicit opt-in for ES6 ("esversion": 6) and does not support JSX, async/await (without hacks), or optional chaining.

// JSHint fails on this without config tweaks:
const data = obj?.prop ?? 'default' // SyntaxError in older JSHint

standard supports modern JS because it’s built on top of eslint under the hood — so it inherits ESLint’s parser capabilities.

jscs never supported ES2015+ fully before deprecation.

🔄 Autofixing Capabilities

eslint --fix automatically corrects many issues (spacing, quotes, semicolons, etc.).

npx eslint src --fix

standard --fix also auto-fixes, since it wraps ESLint.

npx standard --fix

jshint has no autofix feature — it only reports problems.

jscs had limited autofixing before deprecation, but it’s irrelevant today.

📦 Extensibility and Ecosystem

eslint wins decisively here:

Write custom rules using AST traversal.
Use shared configs (eslint-config-prettier, @typescript-eslint/eslint-recommended).
Integrate with Prettier via eslint-config-prettier to disable conflicting rules.

Example custom rule (simplified):

// my-custom-rule.js
module.exports = {
  create(context) {
    return {
      Literal(node) {
        if (typeof node.value === 'string' && node.value.includes('FIXME')) {
          context.report({ node, message: 'Remove FIXME comments' });
        }
      }
    };
  }
};

jshint and jscs offer no plugin system — you’re stuck with built-in rules.

standard allows no extensions — it’s intentionally rigid.

🧪 Real-World Team Scenarios

Scenario 1: Large Frontend Monorepo with React + TypeScript

✅ Only eslint works — due to need for TypeScript parsing, React hooks rules, and custom team policies.
❌ standard lacks TypeScript awareness out of the box.
❌ jshint and jscs can’t parse TS or JSX reliably.

Scenario 2: Small Open-Source Utility Library

✅ standard shines — zero config, consistent output, easy onboarding.
✅ eslint also works if you publish a shareable config.
❌ Avoid jshint if using modern syntax.

Scenario 3: Legacy jQuery Application (ES5)

✅ jshint is sufficient — simple, fast, and matches old-school JS.
✅ eslint works too but may be overkill.
❌ Don’t use standard — it enforces modern style that may clash with legacy patterns.

📊 Summary Table

Feature	`eslint`	`jscs`	`jshint`	`standard`
Actively Maintained	✅ Yes	❌ Deprecated	⚠️ Minimal	✅ Yes
Configurable	✅ Fully	✅ (Historical)	⚠️ Limited	❌ No
Modern JS Support	✅ Full	❌ None	❌ Partial	✅ Full
Autofix	✅ Yes	⚠️ (Historical)	❌ No	✅ Yes
Custom Rules	✅ Yes	❌ No	❌ No	❌ No
TypeScript/JSX	✅ Via plugins	❌ No	❌ No	⚠️ Limited

💡 Final Guidance

For any new professional project: Start with eslint. It’s flexible, future-proof, and integrates with every major toolchain.
If your team hates config debates: Try standard, but verify it supports your stack (e.g., React, TypeScript).
Maintaining old code: jshint is acceptable for ES5-only projects, but plan a migration to ESLint.
Never start a new project with jscs — it’s obsolete.

Remember: A linter’s job isn’t just to catch bugs — it’s to enforce team agreements at machine speed. Choose the tool that grows with your codebase, not one that holds it back.

eslint:
Choose eslint if you need a highly configurable, actively maintained linter with support for modern JavaScript (ES2020+), JSX, TypeScript (via plugins), custom rules, and autofixing. It’s the de facto standard in professional frontend projects and integrates seamlessly with editors and build pipelines.
jshint:
Choose jshint only for legacy projects or environments where minimal configuration and simplicity are prioritized over modern language support and extensibility. It lacks support for many ES2015+ features out of the box and cannot be extended with custom rules or plugins.
standard:
Choose standard if your team prefers zero-configuration, opinionated formatting with consistent defaults and automatic fixes. It enforces a specific style guide (no semicolons, 2-space indents, etc.) and works well for small teams that want to avoid style debates, but offers no customization.
jscs:
Do not choose jscs for new projects — it was officially deprecated in 2016 and merged into eslint. The project is archived on GitHub and no longer receives updates. Existing codebases should migrate to eslint using the provided migration tool.

eslint

jshint

standard

jscs

ESLint

ESLint is a tool for identifying and reporting on patterns found in ECMAScript/JavaScript code. In many ways, it is similar to JSLint and JSHint with a few exceptions:

ESLint uses Espree for JavaScript parsing.
ESLint uses an AST to evaluate patterns in code.
ESLint is completely pluggable, every single rule is a plugin and you can add more at runtime.

Installation and Usage

Prerequisites: Node.js (^20.19.0, ^22.13.0, or >=24) built with SSL support. (If you are using an official Node.js distribution, SSL is always built in.)

You can install and configure ESLint using this command:

npm init @eslint/config@latest

After that, you can run ESLint on any file or directory like this:

npx eslint yourfile.js

pnpm Installation

To use ESLint with pnpm, we recommend setting up a .npmrc file with at least the following settings:

auto-install-peers=true
node-linker=hoisted

This ensures that pnpm installs dependencies in a way that is more compatible with npm and is less likely to produce errors.

Configuration

You can configure rules in your eslint.config.js files as in this example:

import { defineConfig } from "eslint/config";

export default defineConfig([
	{
		files: ["**/*.js", "**/*.cjs", "**/*.mjs"],
		rules: {
			"prefer-const": "warn",
			"no-constant-binary-expression": "error",
		},
	},
]);

The names "prefer-const" and "no-constant-binary-expression" are the names of rules in ESLint. The first value is the error level of the rule and can be one of these values:

"off" or 0 - turn the rule off
"warn" or 1 - turn the rule on as a warning (doesn't affect exit code)
"error" or 2 - turn the rule on as an error (exit code will be 1)

The three error levels allow you fine-grained control over how ESLint applies rules (for more configuration options and details, see the configuration docs).

Version Support

The ESLint team provides ongoing support for the current version and six months of limited support for the previous version. Limited support includes critical bug fixes, security issues, and compatibility issues only.

ESLint offers commercial support for both current and previous versions through our partners, Tidelift and HeroDevs.

See Version Support for more details.

Code of Conduct

ESLint adheres to the OpenJS Foundation Code of Conduct.

Filing Issues

Before filing an issue, please be sure to read the guidelines for what you're reporting:

Frequently Asked Questions

Does ESLint support JSX?

Yes, ESLint natively supports parsing JSX syntax (this must be enabled in configuration). Please note that supporting JSX syntax is not the same as supporting React. React applies specific semantics to JSX syntax that ESLint doesn't recognize. We recommend using eslint-plugin-react if you are using React and want React semantics.

Does Prettier replace ESLint?

No, ESLint and Prettier have different jobs: ESLint is a linter (looking for problematic patterns) and Prettier is a code formatter. Using both tools is common, refer to Prettier's documentation to learn how to configure them to work well with each other.

What ECMAScript versions does ESLint support?

ESLint has full support for ECMAScript 3, 5, and every year from 2015 up until the most recent stage 4 specification (the default). You can set your desired ECMAScript syntax and other settings (like global variables) through configuration.

What about experimental features?

ESLint's parser only officially supports the latest final ECMAScript standard. We will make changes to core rules in order to avoid crashes on stage 3 ECMAScript syntax proposals (as long as they are implemented using the correct experimental ESTree syntax). We may make changes to core rules to better work with language extensions (such as JSX, Flow, and TypeScript) on a case-by-case basis.

In other cases (including if rules need to warn on more or fewer cases due to new syntax, rather than just not crashing), we recommend you use other parsers and/or rule plugins. If you are using Babel, you can use @babel/eslint-parser and @babel/eslint-plugin to use any option available in Babel.

Once a language feature has been adopted into the ECMAScript standard (stage 4 according to the TC39 process), we will accept issues and pull requests related to the new feature, subject to our contributing guidelines. Until then, please use the appropriate parser and plugin(s) for your experimental feature.

Which Node.js versions does ESLint support?

ESLint updates the supported Node.js versions with each major release of ESLint. At that time, ESLint's supported Node.js versions are updated to be:

The most recent maintenance release of Node.js
The lowest minor version of the Node.js LTS release that includes the features the ESLint team wants to use.
The Node.js Current release

ESLint is also expected to work with Node.js versions released after the Node.js Current release.

Refer to the Quick Start Guide for the officially supported Node.js versions for a given ESLint release.

Where to ask for help?

Open a discussion or stop by our Discord server.

Why doesn't ESLint lock dependency versions?

Lock files like package-lock.json are helpful for deployed applications. They ensure that dependencies are consistent between environments and across deployments.

Packages like eslint that get published to the npm registry do not include lock files. npm install eslint as a user will respect version constraints in ESLint's package.json. ESLint and its dependencies will be included in the user's lock file if one exists, but ESLint's own lock file would not be used.

We intentionally don't lock dependency versions so that we have the latest compatible dependency versions in development and CI that our users get when installing ESLint in a project.

The Twilio blog has a deeper dive to learn more.

Releases

We have scheduled releases every two weeks on Friday or Saturday. You can follow a release issue for updates about the scheduling of any particular release.

Security Policy

ESLint takes security seriously. We work hard to ensure that ESLint is safe for everyone and that security issues are addressed quickly and responsibly. Read the full security policy.

Semantic Versioning Policy

ESLint follows semantic versioning. However, due to the nature of ESLint as a code quality tool, it's not always clear when a minor or major version bump occurs. To help clarify this for everyone, we've defined the following semantic versioning policy for ESLint:

Patch release (intended to not break your lint build)
- A bug fix in a rule that results in ESLint reporting fewer linting errors.
- A bug fix to the CLI or core (including formatters).
- Improvements to documentation.
- Non-user-facing changes such as refactoring code, adding, deleting, or modifying tests, and increasing test coverage.
- Re-releasing after a failed release (i.e., publishing a release that doesn't work for anyone).
Minor release (might break your lint build)
- A bug fix in a rule that results in ESLint reporting more linting errors.
- A new rule is created.
- A new option to an existing rule that does not result in ESLint reporting more linting errors by default.
- A new addition to an existing rule to support a newly-added language feature (within the last 12 months) that will result in ESLint reporting more linting errors by default.
- An existing rule is deprecated.
- A new CLI capability is created.
- New capabilities to the public API are added (new classes, new methods, new arguments to existing methods, etc.).
- A new formatter is created.
- eslint:recommended is updated and will result in strictly fewer linting errors (e.g., rule removals).
Major release (likely to break your lint build)
- eslint:recommended is updated and may result in new linting errors (e.g., rule additions, most rule option updates).
- A new option to an existing rule that results in ESLint reporting more linting errors by default.
- An existing formatter is removed.
- Part of the public API is removed or changed in an incompatible way. The public API includes:
  - Rule schemas
  - Configuration schema
  - Command-line options
  - Node.js API
  - Rule, formatter, parser, plugin APIs

According to our policy, any minor update may report more linting errors than the previous release (ex: from a bug fix). As such, we recommend using the tilde (~) in package.json e.g. "eslint": "~3.1.0" to guarantee the results of your builds.

ESM Dependencies

Since ESLint is a CommonJS package, there are restrictions on which ESM-only packages can be used as dependencies.

Packages that are controlled by the ESLint team and have no external dependencies can be safely loaded synchronously using require(esm) and therefore used in any contexts.

For external packages, we don't use require(esm) because a package could add a top-level await and thus break ESLint. We can use an external ESM-only package only in case it is needed only in asynchronous code, in which case it can be loaded using dynamic import().

License

MIT License

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.