recommended vs performant
The two configs share files.includes, the formatter (except trailing commas), and these rules: noForEach,
useLiteralKeys, noCommaOperator, noUnusedVariables, useExhaustiveDependencies, noNonNullAssertion,
noParameterAssign, useTemplate, the style rules promoted to error, noAssignInExpressions, and noExplicitAny.
These settings differ:
| Setting | recommended | performant |
|---|---|---|
javascript.formatter.trailingCommas |
not set (Biome default, all) |
none |
correctness/noUnusedImports |
error, fix: safe |
not set (Biome default: warn) |
correctness/noInnerDeclarations |
not set (Biome default: error) | warn |
suspicious/noConsole |
error; every console method except log is allowed |
not set (console.log accepted) |
suspicious/noVar |
warn | off |
assist.actions.source.organizeImports |
on |
off |
Override: json.parser allows comments and trailing commas for frontmatter.json, .frontmatter/config/**/*.json, .vscode/**/*.json, tsconfig*.json |
yes | no |
Choose
Section titled “Choose”- Pick
recommendedwhen you want unused imports to fail,console.logblocked, and imports sorted bybiome check. - Pick
performantwhen you want trailing commas removed and the rules above relaxed.
Both configs set style/useNodejsImportProtocol to error, so import 'assert' fails in either.
Back to the overview.