SCSS/CSS Intellisense suddenly broken by Some Sass extension in VS Code
Hello everyone. I am asking for help:
The Some Sass extension in VS Code suddenly stopped working, and all Intellisense for SCSS and CSS is now completely broken.
Here’s the full debug output I get:
[Info - 10:21:45 PM] Workspace root file:///c%3A/Users/PC/Desktop/astro-news-website
[Debug - 10:21:45 PM] Applied user configuration
[Debug - 10:21:45 PM] Applied user configuration
[Debug - 10:21:45 PM] Found 202 files, starting parse
You can't have more than one poster comment.
You can't have more than one poster comment.
You can't have more than one poster comment.
You can't have more than one poster comment.
You can't have more than one poster comment.
You can't have more than one poster comment.
You can't have more than one poster comment.
I’ve already tried:
Reinstalling the extension
Running it without SCSS Intellisense
Restarting VS Code and my PC multiple times
Little update: I think there is something wrong with this specific project that crashes the extension - Because in any other project works good
VS Code version: 1.103.2 (x64)
OS: Win 10 22H240 Replies
what happens if you run just the scss intelliesense extension?
it works good
you know what to do
also, i downloaded the project and ... nothing
?? which project? ahaha
some sass
ah you mean the extension
i downloaded the code and tried to find that message
yup
oh thats so strange - anyway i manage to isolate the folder that cause the problem
what was the problem?
I have no idea - i only know that if i remove the folder, the extension works good
😭
well, then what's in the folder?
plenty of container queries and complex mixins
well, time to remove a file at a time
yeah, I was like "oh tonight I am gonna code some cool things" and then vscode drops this
🤣
sometimes, stuff doesn't go as planned
I found the file bro
what was it?
i finally
cool thing of all things
it was something i was gonna to delete
// #region Deprecated
// Todo Da fixare questo giù
// Questi sono i margins inline, se e quando i buttons vengono inseriti nella navigation
////////////////////////////////////////////////////
// // Notes - I don't know where this should be
// // Notes - I wish i can do this in a different way
// //Todo - Da sistemare meglio
// //! Setting inline margins if buttons position it's inside navigation
// @if (true){ // If to do
// $buttons-margins: map.get($carousel-buttons-position-inside-navigation, margins-from-scroll-markers-group-when-default);
// $buttons-width: $carousel-buttons-width;
// @container --carousel-container style(--buttons-position: inside-navigation){
// .carousel::scroll-marker-group {
// margin-inline: calc(
// $buttons-width +
// $buttons-margins -
// 0.95rem // Tokenize?
// );
// }
// }
// }
// @if (true){ // If general behaviour it's NOT Stretch with navigation
// $buttons-margins: map.get($carousel-buttons-position-inside-navigation, margins-from-scroll-markers-group-when-default);
// $buttons-width: $carousel-buttons-width;
// @container --carousel-container
// style(--buttons-position: inside-navigation) and
// style(--scroll-marker-group-orientation: vertical) {
// .carousel::scroll-marker-group{
// margin-inline: calc(
// $buttons-width -
// $buttons-margins -
// 0.95rem // Tokenize?
// );
// }
// }
// }
// We decided to deprecated this ^
// #endregion
it was all comment out like thatthe question is: which part of the file causes that?
this part
the whole block?
mhm i don't know
no it is not the whole block
it's #region actually
//! Setting inline margins if buttons position it's inside navigation <-- this?
nah, that can't be itit's // #region Deprecated
no
that's why it can't be it
no actually it's just the #region block
i don't know
where did you see the messages?
i still see them
remove the
! from the comment
see if that still happensno only thing that fixes it it's removing the #region and #endregion
that sounds like a bug then
you have
// #region
that should be //#region
try without the spacei will, i am gonna take a 5 min break now
go for it
i could smash everything like khabib nurmagomedov right now
or not
anyway no even with //#region it breaks intellisense
but if i remove it completely it works good
removing //#region and //#endregion from that block makes the intellisense come back
also, while having //#region and //#endregion, and hovering on variables or mixins inside the #region i have this
that sounds like a bug then