Closed Hlsgs closed 6 years ago
Can you show your gruntfile settings?
Of course.
I've trimmed out all the unrelated stuff. Also, I've checked with and without grunt-concurrent
and it's unrelated.
Look at the grungfile of the project, this is the key.
https://github.com/sindresorhus/grunt-sass/blob/master/gruntfile.js
The new version needs Node 8 or higher
@Suriv I am using the latest v10.6.0
In the original gruntfile, he adds this:
'use strict';
const sass = require('node-sass');
module.exports = grunt => {
and
implementation: require('node-sass') by implementation: sass
It really is the same as what you have done
Also a change is that it changes dev by compile and the sourceMap option takes it out of dev, see if it looks like it works
All that can't have anything to do with it. I'm not sure what to take away from what you've said.
The issue is that done
is not called when there is an error, meaning grunt-watch still thinks the task is running and wont run another one.
This (https://github.com/sindresorhus/grunt-sass/pull/292) pull request solves the issue.
3.0.1 seems correctly pass sass errors to grunt indeed, but then, after amending the error, grunt-contrib-watch only logs the file change and stops working.