Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community!

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

CSS Sass Basics Add Reusable Logic to Your Sass Handling Errors with @error and @warn

Steve Gallant
Steve Gallant
14,943 Points

Compiler stops and removes styles.css for both @error and @warning

I'm working through the course locally on my workstation. When I use the @error or @warning directives and feed in a bogus argument, the styles.css file actually disappears from the css folder. The compiler spits out an error, but there is nothing in the browser console except stating it cannot find the styles.css.

Update in behavior?

thanks, Steve

Same for me

For me I am using VS Code, and as Bryan Land suggested, I am also running sass --watch scss:css

Bryan Land
Bryan Land
10,306 Points

I want to add that using the @warn directive, it does still compile. This is a peculiar issue but isn't a huge deal. If Guil Hernandez knows anything about it, maybe he will grace us with his presence in this thread! Cheers!

Funny thing, in a later lesson @error and @warn work as it should, but I'm not sure why it works there and not here. I am using VS Code and running sass --watch scss:css

1 Answer

Bryan Land
Bryan Land
10,306 Points

I noticed this as well when using VSCode where if there are no issues, the css output is generated just fine but once you have an error at all, even without inserting debugging directives like @error or @warn, it will delete the output file completely.

Luckily the debug and error messages still appear in the terminal you are running --watch in. Could be related this this bug.

What editors are you using locally?