biome-config

Configure Biome by creating a root biome.json with linter, formatter, and organizeImports sections, then add per-package overrides in each workspace. Use fields for vcs, files, and lint rules to enforce consistent code quality across all packages.

Yes, Biome's organizeImports configuration lets you define import ordering and grouping rules. Configure workspace-specific import guidelines in biome.json and run organize-imports to automatically sort and group imports consistently.

Migrate by mapping your ESLint rules and Prettier formatting preferences into Biome's linter and formatter configuration. Set up a root biome.json with equivalent rules, test with biome check and biome format, then validate against your existing codebase.

Run biome check with verbose output to identify which rules are failing and why. Review your biome.json schema against Biome's documentation, check for conflicting formatter and linter settings, and validate per-package overrides match the root configuration.

Yes, define workspace-specific overrides in each package's biome.json or use the files field in the root configuration to apply different lint rules, formatting styles, and import-organization settings per package while maintaining a shared baseline.

Yes, Biome includes diagnostics and autofix capabilities. Run biome check --fix to automatically correct common linting issues, or use biome format to apply formatting rules, reducing manual code review overhead across your monorepo.