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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃悰 BUG: Intellisense for CSS not working in .astro files #764
Comments
I can't really help without more details (the file where it stops working etc). The CSS intellisense kinda has no state attached to it, so typically it's an unrelated error that would break it, perhaps the compiler failed to parse a file or something. |
Hello @FairyPenguin. Please provide a minimal reproduction using a GitHub repository or at least sharing the file where the issue happen. Issues marked with |
Every .astro file Simply: all the .astro files lose the CSS intellisense. And the only fixation is to restart the Extension. If it happens once in a while I wouldn't report it and Keep with it but it's happening every time I use Astro now. |
I will record a video when this happens again. It's a repeated issue so this will be easy for me to catch it in a Screen Recording, For the Repo as I asked in the other Issue I need an Email Address to send the repo. |
A rproduce! https://github.com/FairyPenguin/astro-reproduce As required, hope this helps, because now the extension or the language server is too laggy that I had to use .css files to work around this. |
Thank you, I'll take a look as soon as possible |
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
npm init astro
using templateThe text was updated successfully, but these errors were encountered: