Skip to content
Sarj Code Standards

no-oxlint-directive

Write every suppression directive with the eslint-* spelling.

oxlintDirective Rule source Tests Catalog JSON

Why

Oxlint honors both oxlint-* and eslint-* directive comments. With two spellings, finding every suppression in a repository takes two searches, and the same directive reads differently from file to file. One spelling keeps suppressions findable and reviewable alike; eslint-* is the spelling existing code already uses.

Fix

Rename the directive prefix from oxlint- to eslint-; the rule list and the description stay as they are.

Examples

Before — flagged An Oxlint-spelled directive
src/report.ts
// oxlint-disable-next-line no-console -- the CLI prints its report
console.log(report);
After — preferred The ESLint spelling
src/report.ts
// eslint-disable-next-line no-console -- the CLI prints its report
console.log(report);
Autofix output
src/report.ts
// eslint-disable-next-line no-console -- the CLI prints its report
console.log(report);

References