ultracite

You can set up zero-config linting by running `bunx ultracite init` to bootstrap your JavaScript or TypeScript project with preset linter configurations. It automatically applies an opinionated baseline to enforce code quality without manual setup.

Yes, the tool works with Biome, ESLint, and Oxlint. It detects the active linter in your JavaScript or TypeScript project by checking for the presence of `biome.jsonc`, `eslint.config.mjs`, or `oxlint.config.ts` files.

Automating code formatting is best handled by applying a zero-config, opinionated baseline during initialization. This enforces coding standards across your codebase using check, fix, and doctor commands to maintain quality.

You can troubleshoot linter setup issues in your TypeScript project by running the built-in doctor command. This provides clear guidance for resolving common configuration problems within the Biome, ESLint, or Oxlint ecosystems.

Yes, you must declare Ultracite in devDependencies to use it for project setup. Once added, it automates zero-config linting and formatting workflows during initialization, checking, fixing, and troubleshooting.

Formatting may fail if the active linter is not detected. Ensure your project contains `biome.jsonc`, `eslint.config.mjs`, or `oxlint.config.ts`, as the tool requires these files to identify the active linter and apply the correct formatting rules.