You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using pre-commit hook, where I've overridden the entry, to benefit from `--config-path` argument, as my config file is in a subdirectory.
CLI:
Version: 1.6.2
Color support: true
Platform:
CPU Architecture: x86_64
OS: linux
Environment:
BIOME_LOG_DIR: unset
NO_COLOR: unset
TERM: "xterm"
JS_RUNTIME_VERSION: "v20.11.1"
JS_RUNTIME_NAME: "node"
NODE_PACKAGE_MANAGER: "npm/10.2.4"
Biome Configuration:
Status: Loaded successfully
Formatter disabled: true
Linter disabled: false
Organize imports disabled: true
VCS disabled: false
Workspace:
Open Documents: 0
What happened?
I use JSONC configuration (as generated by biome init --jsonc)
If I run biome with the --config-path argument, it does not actually find the config file and fails with error Biome couldn't read the following file, maybe for permissions reasons or it doesn't exists: ./src/rome.json
If I rename biome.jsonc to biome.json, no error is reported
Expected result
Both biome.json and biome.jsonc should be valid configuration files.
Code of Conduct
I agree to follow Biome's Code of Conduct
The text was updated successfully, but these errors were encountered:
Environment information
What happened?
biome init --jsonc
)--config-path
argument, it does not actually find the config file and fails with errorBiome couldn't read the following file, maybe for permissions reasons or it doesn't exists: ./src/rome.json
biome.jsonc
tobiome.json
, no error is reportedExpected result
Both
biome.json
andbiome.jsonc
should be valid configuration files.Code of Conduct
The text was updated successfully, but these errors were encountered: