-
-
Notifications
You must be signed in to change notification settings - Fork 41
Issues: biomejs/biome-vscode
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
🐛 Biome extensions keeps shutting down in vscode (Pre-release version)
Needs reproduction
Needs a reproduction
#578
opened Apr 27, 2025 by
mfonisoebong
1 of 3 tasks
🐛Biome Extension with Ivanti Security on Windows
Triage
#548
opened Mar 28, 2025 by
tmeindle
1 of 3 tasks
🐛
biome.projects
setting used in pre-release version, but default settings are applied instead
Triage
#547
opened Mar 28, 2025 by
TakashiAihara
1 of 3 tasks
🐛 Extension does not find the biome binary if it depends on the CWD
Needs more details
Triage
#528
opened Mar 13, 2025 by
TimDiekmann
1 of 3 tasks
Use
workspace/configuration
response for providing the manual configuration path
#513
opened Mar 2, 2025 by
siketyan
🐛 disabled linter doesn't show errors but autofixes them anyways
Linux
#491
opened Feb 7, 2025 by
Akuukis
1 of 3 tasks
🐛 Biome not properly formatting workspace files
2.x
Triage
#410
opened Oct 21, 2024 by
jason-slash
3 tasks
🐛
biome.requireConfigFile
Ignored When Opening Single File in VSCode
Prerelease
Triage
#390
opened Oct 9, 2024 by
LucasOe
1 of 3 tasks
🐛 biome.json looks to be ignored periodically
2.x
Triage
#304
opened Aug 16, 2024 by
Hoshock
1 of 3 tasks
🐛 Biome applies unsafe fixes inside liveshares
2.x
Bug confirmed
Report has been confirmed as a valid bug
Help wanted
External contributions are welcome
#119
opened Feb 8, 2024 by
gustaferiksson
ProTip!
Add no:assignee to see everything that’s not assigned.