Marcin Cieślak

@chriseppstein Can you try applying https://github.com/sass/libsass/pull/1289 to libsass? May not fix all quoted-vs-unquoted string issues, but certainly lets us pass them over to node and back.

Ah now I start to understand. So maybe "String_Quoted" should not be derived class of String_Constant? Are they in some circumstances interchangeable? Because in that case we should use common...

Sorry for keeping you waiting @xi I remember I was also very confused trying to start with eyeglass. Can you give me short a short example how things get easier?...

@montchr can you try to prepare some minimal case to reproduce the problem?

The good news is that with ``` sassc: 3.3.6-11-g077a libsass: 3.3.6-92-g014a61 sass2scss: 1.0.6 sass: 3.4 ``` I cannot reproduce this problem anymore. Running `sassc invalid.scss` produces: ``` Error: Invalid CSS...

Running `node-sass` (on FreeBSD): ``` node-sass 3.8.0 (Wrapper) [JavaScript] libsass 3.3.6 (Sass Compiler) [C/C++] ``` The output is: ``` { "formatted": "Error: Invalid CSS after \"f\": expected 1 selector or...

Can you check if grunt is not installing an older version of node-sass by chance?

I have used the following `package.json`: ``` { "name": "2d725069a91abc25f8db3462342f98f6", "version": "1.0.0", "description": "", "main": "Gruntfile.js", "scripts": { "test": "echo \"Error: no test specified\" && exit 1" }, "repository": {...

er, can you take nvm out of the way?

Since it looks like an environmental issue to me, can you please follow https://github.com/sass/node-sass/blob/master/TROUBLESHOOTING.md and post the output?