Skip to content
Ultracite
Esc
↑↓navigate↵open⌘Jpreview
On this page

Migrate from Stylelint

Replace standalone Stylelint setup with Ultracite while keeping CSS linting standards aligned with the rest of your frontend tooling.

If you’re already using Stylelint and want to switch to Ultracite’s preconfigured setup, this guide will help you migrate while preserving your styling standards.

Why Migrate to Ultracite?

  • Multiple Providers: Choose between Biome, ESLint + Prettier + Stylelint, or Oxlint
  • Zero Configuration: Ultracite provides highly configured presets for each provider
  • Editor Integration: Built-in support for AI-powered editors (Cursor, Windsurf, GitHub Copilot)
  • Consistent Workflow: Standardized setup across projects and teams
  • Maintained Rules: Regular updates with new best practices

Before You Start

Make sure you have:

  • An existing project using Stylelint
  • Node.js 20+
  • A Stylelint configuration file (e.g., .stylelintrc, stylelint.config.js)

Migration Options

The fastest way is to run the automatic setup script.

npx ultracite init
pnpm dlx ultracite init
yarn dlx ultracite init
bunx ultracite init

This will:

  • Prompt you to choose a linting provider (Biome, ESLint, or Oxlint)
  • Install Ultracite and the necessary dependencies
  • Create or merge your linter configuration with Ultracite’s preset
  • Merge your existing .vscode/settings.json with Ultracite’s preset
  • Enable strictNullChecks in your existing tsconfig.json files (skipped if your project has none)
  • Set up editor integrations

If you switch to Biome or Oxlint (which have built-in CSS support), Ultracite automatically removes the existing Stylelint configuration. This will:

  • Remove Stylelint and any related dependencies
  • Remove any Stylelint configuration files

If you also select an editor to configure, your .vscode/settings.json is rewritten to match the new toolchain.

If you choose ESLint as your provider, Ultracite will configure Stylelint alongside ESLint using Ultracite’s preset.

Option 2: Manual Migration

If you prefer more control over the process, follow the Manual Setup steps and manually remove Stylelint and its configuration files.

After the migration, restart your editor to ensure the new configuration is applied.

Was this page helpful?