🐛 biome processing .vscode/*.txt that it shouldn't

unional commented 5 hours ago

Environment information

CLI:
  Version:                      1.9.4
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           linux

Environment:
  BIOME_LOG_PATH:               unset
  BIOME_LOG_PREFIX_NAME:        unset
  BIOME_CONFIG_PATH:            unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v20.18.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "pnpm/9.12.2"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 false

Workspace:
  Open Documents:               0

What happened?

It is scanning and processing .txt file it shouldn't.

https://github.com/repobuddy/storybook-addon-vis/tree/biome-txt

pnpm i
pnpm check

The repo above has ignored any addition configs that doesn't matter already.

Expected result

no error

Code of Conduct

[X] I agree to follow Biome's Code of Conduct

ematipico commented 5 hours ago

What kind of error does Biome output?

unional commented 4 hours ago

Things like string should be in qoutes. Seems like biome is treating them like js/ts/json file

ematipico commented 3 hours ago

Is it possible that your editor is mapping those files to another language?

Is it possible that there's an extension that does that?

To make sure it's Biome and not something in your editor, always use the CLI.

biomejs / biome