src/content/docs/linter/rules/no-excessive-classes-per-file.mdx
import { Tabs, TabItem } from '@astrojs/starlight/components';
<Tabs> <TabItem label="JavaScript (and super languages)" icon="seti:javascript"> :::caution This rule is part of the [nursery](/linter/#nursery) group. This means that it is experimental and the behavior can change at any time. ::: ## Summary - Rule available since: `v2.3.12` - Diagnostic Category: [`lint/nursery/noExcessiveClassesPerFile`](/reference/diagnostics#diagnostic-category) - This rule doesn't have a fix. - The default severity of this rule is [**information**](/reference/diagnostics#information). - Sources: - Same as [`max-classes-per-file`](https://eslint.org/docs/latest/rules/max-classes-per-file){
"linter": {
"rules": {
"nursery": {
"noExcessiveClassesPerFile": "error"
}
}
}
}
Enforce a maximum number of classes per file.
Files containing multiple classes can often result in a less navigable and poorly structured codebase. Best practice is to keep each file limited to a single responsibility.
class Foo {}
class Bar {}
class Foo {}
The following options are available:
maxClassesThis option sets the maximum number of classes allowed in a file. If the file exceeds this limit, a diagnostic will be reported.
Default: 1
{
"linter": {
"rules": {
"nursery": {
"noExcessiveClassesPerFile": {
"options": {
"maxClasses": 2
}
}
}
}
}
}
class Foo {}
class Bar {}
class Baz {}