Environment information

❯ npx biome rage
CLI:
  Version:                      2.0.5
  Color support:                true

Platform:
  CPU Architecture:             aarch64
  OS:                           macos

Environment:
  BIOME_LOG_PATH:               unset
  BIOME_LOG_PREFIX_NAME:        unset
  BIOME_CONFIG_PATH:            unset
  BIOME_THREADS:                unset
  NO_COLOR:                     unset
  TERM:                         xterm-ghostty
  JS_RUNTIME_VERSION:           v22.13.1
  JS_RUNTIME_NAME:              node
  NODE_PACKAGE_MANAGER:         npm/10.9.2

Biome Configuration:
  Status:                       Loaded successfully
  Path:                         biome.jsonc
  Formatter enabled:            true
  Linter enabled:               true
  Assist enabled:               true
  VCS enabled:                  true

Workspace:
  Open Documents:               0

What happened?

We recently updated to Biome 2.x and have seen a major regression in the time it takes to run a simple format command:

• Single-file formatting time on Biome 1.9.4: 2ms
• Single-file formatting time on Biome 2.x (applies from 2.0.0 to latest 2.0.5): 1s

this is entirely from running npx biome format --write src/cli/commands/circleci/get-project-settings.ts in our large monorepo to format a single file, and reading Biome's timing report.

this seems to be coming from some kind of initialization time, because total time to format the entire codebase is not significantly up. It's particularly noticeable in scripts we run that format many single files in quick succession.

We have many files in our monorepo, could it be a new file-globbing thing during initialization?

Expected result

Same run time as in 1.x.

Code of Conduct

• I agree to follow Biome's Code of Conduct