-
-
Notifications
You must be signed in to change notification settings - Fork 858
Labels
A-CoreArea: coreArea: coreS-Bug-confirmedStatus: report has been confirmed as a valid bugStatus: report has been confirmed as a valid bugworkaround
Description
Environment information
CLI:
Version: 2.2.0
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-256color
JS_RUNTIME_VERSION: unset
JS_RUNTIME_NAME: unset
NODE_PACKAGE_MANAGER: unset
Biome Configuration:
Status: Loaded successfully
Path: biome.json
Formatter enabled: true
Linter enabled: true
Assist enabled: true
VCS enabled: true
Workspace:
Open Documents: 0
What happened?
I setup a repository using better-t-stack with the latest versions of Biome and Ultracite. I am unable to use file.includes. No matter what I put in my biome.json, especially negations (e.g. "!bun.lock") it seems biome is still linting and formatting those files and showing problems/errors/warnings. I need to, for example, exclude my shadcn ui package completely from biome, and this makes biome unusable.
Here is my config file:
{
"$schema": "https://biomejs.dev/schemas/2.2.0/schema.json",
"files": {
"ignoreUnknown": true,
"includes": [
"**",
"!bun.lock",
"!**/.next",
"!**/dist",
"!**/.turbo",
"!**/dev-dist",
"!**/.zed",
"!**/.vscode",
"!**/routeTree.gen.ts",
"!**/src-tauri",
"!**/.nuxt",
"!bts.jsonc",
"!**/.expo",
"!**/.wrangler",
"!**/.source",
"!**/tsconfig.*",
"!**/__generated",
"!node_modules",
"!**/node_modules",
"!**/ui/src/components"
]
},
"vcs": {
"enabled": true,
"clientKind": "git",
"useIgnoreFile": true
},
"extends": ["ultracite"]
}
Expected result
It should not show errors or lint or format the files that are ignored via file.includes, but it does anyways.
Code of Conduct
- I agree to follow Biome's Code of Conduct
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-CoreArea: coreArea: coreS-Bug-confirmedStatus: report has been confirmed as a valid bugStatus: report has been confirmed as a valid bugworkaround