-
-
Notifications
You must be signed in to change notification settings - Fork 541
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
🐛 Latest version (1.7.2) keeps crashing #2681
Comments
I have the same issue too.
|
This might be caused by some panic when the lsp is analyzing an opened file, so it would be much helpful if someone can provide the opened file/code when the error shows, so we can know which one caused it. It will also be helpful to try using the CLI ( |
It crashes with a Next.js project, with React code. Just with clicking update, it crashes:
Running
A file example of crashing:
But if I restart and repone the file several times, it doesn't crash after a while... |
Now I can't even choose the 1.7.1 version... when I click in the extension does nothing (I've reinstalled several times). |
Errors are not the problem. I was expecting there may be some program crashes (panics) that cause the server to shutdown.
The extension will install the latest biome when it cannot find one in your system path or in your project dependencies. So I think you can just change the version of biome in your project or in global to force the extension to use that version. |
Have you tried disabling the linter and/or the formatter and/or the import organizer and see if the error persists? This is hard to help you without more precise information... Could you provide us the file that makes the Biome LSP crashes? |
I've always used Biome with the VSC without any Biome packing or CLI, so for me the options are enable or disable the extension. I'm 100% sure that before the 1.7.2 it has never crashed, and I've been using Biome at least 3-4 months. Above I've provided one file that causes the crash, I would be happy to provide more info, but I need to now exactly the steps to provide it! |
Before, if I clicked the extension, it showed me a list of all the versions. Now shows nothing. Very weird. Maybe is because I installed the CLI via homebrew to run the command you said me. Edit: okay I now understand, always I've been using the binary downloaded by the extension, so the installation of the CLI deleted every binary. Now I've to added biome to the package.json to be able to use the 1.7.1. |
After some testing, it crashes when importing |
@angel-luis can you please provide us with some logs? You can retrieve them manually: https://biomejs.dev/guides/integrate-in-editor/#daemon-logs Please make sure to copy the logs written right before the extension crashes |
Cleaned log: |
Thanks for the log, this was really helpful! Biome crashes because of #2659 (TLDR: Biome crashes on conditional types with TypeScript |
Thanks to you and the rest of the team, then we will wait to the patch! 👍 |
VS Code version
1.88.1
Extension version
2.2.2
Biome version
1.7.2
Operating system
Description
The extension stops to work after some minutes.

Steps to reproduce
I've upgraded and also tried to reinstall the extension
Expected behavior
Don't crash, with the 1.7.1 doesn't crash.
Does this issue occur when using the CLI directly?
Not sure / Not applicable
Logs
The text was updated successfully, but these errors were encountered: