Skip to main content
ESLint Interlace
Plugin: conventions

Rules

All ESLint rules provided by eslint-plugin-conventions

9 Rules Available

Team-specific disciplinary patterns and code conventions.

All Rules

Legend: Type-unaware Type-awareRecommendedFixableSuggestionsWarns
Rule🧠💼🔧💡⚠️Docs
consistent-existence-index-check

Enforce consistent style for checking if an element exists in an array

🟢
expiring-todo-comments

Add expiration conditions to TODO comments to prevent forgotten tasks. This rule is part of eslint-plugin-conventions and provides LLM-optimized error messa

🟢
filename-case

Enforce filename case conventions for consistency across your codebase

🟢
no-commented-code

ESLint Rule: no-commented-code with LLM-optimized suggestions and auto-fix capabilities.

🟢
no-console-spaces

Disallow leading/trailing whitespace in console arguments. This rule is part of eslint-plugin-conventions.

🟢
no-deprecated-api

Prevent usage of deprecated APIs with migration context and timeline. This rule is part of eslint-plugin-conventions and provides LLM-optimized error messag

🟢
no-json-schema-tags

Disallow JSON Schema keywords (e.g. @minimum, @maximum, @pattern, @format) used as JSDoc tags.

🟢
prefer-code-point

Prefer String.codePointAt() over String.charCodeAt(). This rule is part of eslint-plugin-conventions.

🟢
prefer-dependency-version-strategy

Enforce consistent version strategy (caret ^, tilde ~, exact, range, or any) for package.json dependencies. Pairs with a lockfile-alignment check to give complete dependency validation.

🟢
prefer-dom-node-text-content

Prefer textContent over innerText. This rule is part of eslint-plugin-conventions.

🟢
require-data-testid

Require stable data-testid attributes on interactive elements for end-to-end test reliability

🟢
Showing 11 of 11 rules

On this page