Errors no longer thrown

[Francisc]

Hello,

I just updated to latest version and noticed that errors are no longer thrown.
For example, if I assign a variable name that does not exist, the task no longer beeps.

What's up?

[sindresorhus]

Works for me:

Running "sass:compile" (sass) task
Warning: /Users/sindresorhus/dev/grunt-sass/test/fixtures/test.scss:7: error: unbound variable $green
 Use --force to continue.

Aborted due to warnings.

What output are you getting?

[Francisc]

Hey. Hm, it shows as OK but doesn't actually compile.
So the CSS file from the last compilation is kept.

Running "watch" task
Waiting...
>> File "sass\components\_tables.scss" changed.
Running "sass:watcher" (sass) task
Completed in 0.588s at Thu Jul 10 2014 16:49:50 GMT+0300 (GTB Daylight Time) - Waiting...

[Francisc]

Actually, here's just the grunt-sass task running:

With errors:

Running "sass:build" (sass) task

Without errors:

Running "sass:watcher" (sass) task
File css/style.css created.
File css/style.css.map created.

Done, without errors.

Seems to fail silently?

[Francisc]

Some background:
Windows 7x64 (=Windows 448?)
Node v0.10.26
grunt-cli v0.1.13
grunt v0.4.5
grunt-sass 0.14.0
Call of Duty Ghosts 3.13.123

[sindresorhus]

Then that's a node-sass issue. I just pass the errors along.

https://github.com/andrew/node-sass

[Francisc]

Hm, OK. Thank you.

[Francisc]

Here's the issue: sass/node-sass#361

If you want source maps, you lose error reporting with the latest version.

Thanks for pointing me in the right direction.

[stevenbriscoeca]

Thanks, I had the same problem

[aminnaggar-fuzzy]

Thanks had the same issue 😄