language-tools: 🐛 BUG: Intellisense for CSS not working in .astro files

Describe the Bug

In a nutshell: .astro files lose the Intellisense for CSS. And the only solution is to restart the extension.

it happened many times, I checked every possible cause from my side but none

Today it happened again I did a basic test and enabled the CSS in file associations for the .astro files CSS Intellisense works back with no problem.

IS there are any steps or methods I can do or use when i encounter this again to check the reason.

Steps to Reproduce

  1. npm init astro using template <NAME>
  2. …
  3. …
  4. …
  5. Error! Describe what went wrong (and what was expected instead)…

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 18 (8 by maintainers)

Most upvoted comments

The issue you linked is not the same one, the users in the screenshot are reporting about new files not appearing in auto imports (which has been mostly fixed already), not that they’re losing all kinds of intellisense, which is what you seem to be reporting.

Same thing for the tsserver crashes, it’s not the same issue. The tsserver can crash without the language server stopping, and vice versa.

I tried on Arch Linux, last version of everything (as expected on Arch)

Please understand that I am alone on this project, it is not my main project at Astro (Astro itself is), no one else in the Astro team works on it and I receive 1 or 2 external contributions per year.

I’m trying my best to fix people’s issues, I do not have the time to do 1:1 calls regarding people’s specific setups when the issues are this isolated. Thousands and thousands of people use this project every day, if an issue like was super prevalent, there would be hundreds of reports.

image

So until last March users were still reporting the same issue !!

Now I’m really confused you said you did test on every OS, and users here saying they face it on every OS?!

Bottom Line: There is a real issue with the LSP or Astro Extension or maybe both, you yourself can’t reach the issue OK fine, But others are facing it and it’s real you can’t reproduce it OK fine but it’s happening to others. End of line.

And for the record a better approach for solving this was to pair with a user facing the issue not a reproduce, because it’s look like the tests you did with every OS as you aid wasn’t valid and mocking the same environment,So it would far better if someone from the Astro team did a pair session ans see the issue live which will give a better understanding and actual facing of what is happening. A re produce here is not much useful, because it’s like a OS/System related issue.