Skip to content

[feat] recognize Biome as a valid linter/formatter alternative to ESLint + Prettier #166

@HeikoGr

Description

@HeikoGr

Summary

Biome is a modern, fast, all-in-one toolchain that replaces both ESLint and Prettier with a single dependency and zero-configuration defaults. Currently the pipeline flags these modules with:

"No ESLint configuration was found. ESLint is very helpful, it is worth using it even for small projects."

This is a false negative: the module does have a linter — just not ESLint.


Requested Changes

1 — Pipeline: detect Biome as a linting/formatting setup

When checking for a linter/formatter, also recognize the presence of any of the following Biome config files:

  • biome.json
  • biome.jsonc

If one of these files is found, the module should be considered to have a linting setup and the "No ESLint configuration was found" hint should not be emitted.

2 — Update guides/README.md

In the hint section for "No ESLint configuration was found", mention Biome as an alternative:

To get started with a linter, check out ESLint or, as a modern all-in-one alternative, Biome.


Why Biome?

ESLint + Prettier Biome
Dependencies 2+ packages, plugin ecosystem 1 package, no plugins needed
Config format eslint.config.mjs + prettier.config.js single biome.json / biome.jsonc
Speed moderate ~10× faster (Rust-based)
Formatting Prettier built-in formatter
Linting ESLint built-in linter
Node.js version requirement ≥ 18.18 ≥ 14 (native binary)

Additional context

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions