Skip to content

Upgrade Biome to 2.5.11 and make CI actually run it - #89

Open
arrufat wants to merge 1 commit into
mainfrom
upgrade-biome-2
Open

Upgrade Biome to 2.5.11 and make CI actually run it#89
arrufat wants to merge 1 commit into
mainfrom
upgrade-biome-2

Conversation

@arrufat

@arrufat arrufat commented Sep 2, 2026

Copy link
Copy Markdown
Collaborator

What

  • CI was a no-op. npx biome ci . resolves the unrelated biome npm package (an env-var manager), not @biomejs/biome, so the lint job passed in seconds without linting anything. The workflow now installs Biome through biomejs/setup-biome and runs biome ci . directly.
  • Pin @biomejs/biome to 2.5.11 (exact, as Biome recommends) and drop the npx / yarn dlx indirection from the package scripts.
  • Migrate biome.json to the 2.x schema with biome migrate (files.ignorefiles.includes, organizeImportsassist).
  • Biome 2 parses CSS, so enable css.parser.tailwindDirectives for the @apply / @tailwind rules in src/styles and globals.css. The CSS files needed no reformatting.
  • Apply the fixes biome check --write reports on the existing sources: import ordering, import type, and formatting in six files. No behaviour changes.

biome ci . --diagnostic-level=error is clean on this branch.

CI ran 'npx biome ci .', which resolves the unrelated 'biome' npm package
rather than @biomejs/biome, so the lint job passed without checking
anything. Install Biome through biomejs/setup-biome instead and pin the
version.

Migrate biome.json to the 2.x schema, enable Tailwind directives now that
Biome parses CSS, and apply the formatting and import-order fixes the new
version reports.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant