Sass always seems so nice to use but crashes on me often. Currently crashed and need to find fix

1

Hey everyone, Sass is awesome especially when used with BEM to keep your code nice and readable throughout.

However I find when I comment out large sections of the code it sometimes crashes Sass. Is this normal?

Right now in my main.css file I see a error message of,

“/* No CSS //# sourceMappingURL=main.css.map */”

Any idea easiest fix for this. All my sass files were working fine, commented some stuff out and then bam.

Would love if someone had an answer for this.

Thanks!

2

Hello @Dobs,

Can you test if the code crashes in codepen.io and share the code there?
I could take a look.

1 Like
3

Hey there,

how do you convert from SASS to CSS?
Do you use codepen or a whole toolchain to do this?

1 Like
4

I tried but theres multiple components so its giving me error after error in codepen because the variables arent linked to anywhere.

5

Its in Visual Studio Code with the extension Live Sass Compiler.

6

I moved on from that last project I am actually back today because I am having the same issue with Sass annoying the hell out of me lol.

I looked and all my closing brackets seem to be in place as that’s usually an issue that could cause an error but in this case that doesn’t seem to be it.

It just says “error” in the bottom toolbar of VS Code. Is there anyway to look further into this to see what’s going on? Its so frustrating. Everything working fine then all the sudden it just stops compiling. I go to my body {} code block to try display: none and just get an error, that won’t even work.

7

Yeah, that sounds annoying.

There should be some logs in your VSCode config folder, e.g. for me on Linux something like this /home/yourusername/.config/VSCodium/logs/.

There should be something similar on Windows and Mac.

I use VSCodium, the default version should be something like VSCode, Code, Code-OSS.