vscode-live-sass-compiler
vscode-live-sass-compiler copied to clipboard
Issue with css grid (ie) and live sass compiler autoprefix
Hi everyone,
In the setting.json of my workspace (vscode editor) I set liveSassCompile.settings.autoprefix
to defaults, that keyword support also Ie 11.
###Now for example we have this code:
.hero { grid-template-columns: repeat(2,1fr); }
###When we compile it, we will have:
.hero { -ms-grid-columns: (1fr)[2]; grid-template-columns: repeat(2, 1fr); }
And vscode tell me that is an error ] expected
.
How I can resolve that? That behavior fills my stylesheet with a lot of errors.
I think the problem is that this plugin is using an old sass.js version that hasn't updated since 2018.
If someone can update this project, it would be nice. Sadly I can't code.
My fix, for now, is to replace all the "repeats" with fully stated values. So instead of .hero { grid-template-columns: repeat(2,1fr); }
You need .hero { grid-template-columns: 1fr 1fr; }
Otherwise, find a new way to compile scss
You can install Dart SASS through this article https://stackoverflow.com/questions/51571814/how-to-install-dart-sass/52063522
you don't need Live Sass Compiler now and there are no issues because you can use latest Sass
New way to compile scss: Installed Dart SASS through this article https://stackoverflow.com/questions/51571814/how-to-install-dart-sass/52063522
Now it's much easier to compile. I don't need Live Sass Compiler and there are no issues because you can use latest Sass
Hey thanks, gonna research that.
But I just learned NodeJS and NPM and used Gulp to automate the process. Every time I save a .scss file it's gonna process it and minify it and with another package it also autoprefixes css properties
So I think that I'm going to stick with this.
can confirm it break grid-template-columns and i moved all my workflow to gulp-sass.
Ok, thank you guys, Do you think that I have to close the issue (because there is no solution) or keep it open?
Let it open for now since it isn't actually fixed and the solution would be to add updated autoprefixer to this compiler. Which shouldn't be hard to do.
I had the same error today, so annoying
any news to this issue?