[Biome] No longer working with v2
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript, vim
- Domain
- tooling
Research direction
Start by reproducing the failure with the reported ALE commit, Vim version, vimrc settings, and biome lint --config-path ~/.config/biome/biome.json advertisement.ts command. Compare the working command with how ALE invokes Biome for TypeScript, including the ale_biome_lsp_project_root setting; done means Biome v2 linting works in Vim with the documented configuration.
Written by the indexing model from the issue text.
Description
ALE commit: edccdfa9efb7a4b37fb846e55b2137b55275d39e
Vim: 9.1.1497-1
Since Biome version 2, the linter no longer works for me although I updated the configuration file. Running biome lint --config-path ~/.config/biome/biome.json advertisement.ts works. However, in Vim it does not.
Relevant sections from my vimrc.
let g:ale_linters =
\{
\ 'bib': ['bibclean'],
\ 'cpp': ['clangtidy'],
\ 'cmake': ['cmake_lint'],
\ 'css': ['stylelint'],
\ 'desktop': ['desktop_file_validate'],
\ 'gitcommit': ['gitlint'],
\ 'html': ['htmlhint', 'tidy'],
\ 'java': ['javac', 'pmd'],
\ 'json': ['jq'],
\ 'mail': [],
\ 'make': ['checkmake'],
\ 'markdown': ['markdownlint'],
\ 'PKGBUILD': ['shell', 'shellcheck'],
\ 'po': ['msgfmt'],
\ 'python': ['bandit', 'mypy', 'pycodestyle', 'pydocstyle', 'pyflakes', 'pyright', 'ruff', 'vulture'],
\ 'sh': ['shell', 'shellcheck'],
\ 'systemd': ['systemd_analyze'],
\ 'tex': ['chktex'],
\ 'text': [],
\ 'toml': [],
\ 'typescript': ['biome'],
\ 'vim': ['vint'],
\ 'xml': ['xmllint'],
\ 'yaml': ['yamllint'],
\ 'zsh': ['shell', 'shellcheck']
\}
""" typescript
let g:ale_biome_lsp_project_root = $XDG_CONFIG_HOME . '/biome/' " Commenting out does still not work.
Consider that I tried to comment out the setting ale_biome_lsp_project_root.
@redbmk Does it still work for you? Do you know a solution? Am I doing something wrong?
- Dominant language
- Vim Script
- Stars
- 14k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dense-analysis/ale
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
dense-analysis/ale#5181 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dense-analysis/ale#5180 · 1 comment ·
-
new tool
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
dense-analysis/ale#5176 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 75/100
dense-analysis/ale#5174 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
dense-analysis/ale#5158 ·
All issues in dense-analysis/ale
Similar issues
-
bug parity
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
WenyuChiou/agent-board#1489 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
ScoopInstaller/Extras#19364 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
osrep/Runes2P.jl#279 ·
Maintainers usually reply within 1 day
-
Incorrect Ruff version demandedPossibly taken @FrancescoPezzella claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
zarr-developers/VirtualiZarr#1160 ·
Maintainers usually reply within 3 days
-
area: sdk bug complexity: trivial
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
accensa/x402-facilitator-stellar#697 ·
Maintainers usually reply within 1 day