What's going on with Sass?

Question

css

Hello.
Lately, the Sass plugin has been acting very strangely. I 'm deploying the project from Yeoman (webapp) , the problem is that after writing the code and saving it, errors get out Screenshot of errors , and the code itself is without errors. So you can, for example, save 5 times in a row and sooner or later it will stop giving an error, "it just chews the code" and everything works fine, but the code has not changed.
Has anyone experienced a similar problem or know what could be causing it? Working with such errors has become simply unbearable :(

Answer 1

I had the exact same bug. I compiled sass via Prepros (gui, everything is via gulp). Code edited in Sublime. And here, too, when I saved often and quickly - the imported files turned out to be unreadable for some reason. Switched to Atom - the problem is gone. It seems that periodically after saving the file, it is blocked by the file system for some unknown reason.

Answer 2

If you are using Sublime, then add the line "atomic_save": true in the settings, and the problem will be solved.. in other editors, I think this problem is not

Answer 3

It also happens to me, only I re-save once everything works. It seems to me that it's just some kind of version conflict, but I'm too lazy to update everything

Answer 4

it was strange, but it was decided by adding "use strict" to the gulpfile at the top, and the import itself
- without quotes and underscores, it finds the file itself