Integrate Biome into Nx monorepos with deterministic setup, caching, migration from ESLint and Prettier, and plugin-based inferred tasks; use when adding Biome, replacing ESLint/Prettier, tuning cache inputs, or scaling lint and format workflows across projects.
Overall
score
100%
Does it follow best practices?
Validation for skill structure
Use this guide when you need advanced configuration details beyond the SKILL hub.
Create and maintain one root biome.json as the default authority:
{
"$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
"files": {
"ignoreUnknown": false
},
"formatter": {
"enabled": true,
"indentStyle": "space",
"indentWidth": 2
},
"linter": {
"enabled": true,
"rules": {
"recommended": true
}
}
}Ensure lint and format targets include config and dependency inputs:
{
"targetDefaults": {
"biome-lint": {
"cache": true,
"inputs": [
"default",
"^default",
"{workspaceRoot}/biome.json",
{ "externalDependencies": ["@biomejs/biome"] }
]
},
"biome-format": {
"cache": true,
"inputs": [
"default",
"^default",
"{workspaceRoot}/biome.json",
{ "externalDependencies": ["@biomejs/biome"] }
]
}
}
}recommended: true as baseline.Example scoped override (temporary migration guardrail):
{
"overrides": [
{
"includes": ["apps/legacy/**"],
"linter": {
"rules": {
"style": {
"noNonNullAssertion": "off"
}
}
}
}
]
}nx run-many -t biome-lint instead of ad hoc per-project loops.nx reset) after plugin or target definition changes.biome.json exists at workspace root.biome-lint and biome-format are cache-enabled.Install with Tessl CLI
npx tessl i pantheon-ai/nx-biome-integration@0.1.0