Open dmartin-gh opened 8 years ago
It's not only Gruntfile.js There are plenty options: .eslintrc .jshintrc and others. So the best if there would be an options to define that for particular task on changing some files cache must be cleaned. E.g.:
newer: {
options: {
...
revalidate: {
"eslint": ['.eslintrc', '.eslintignore'],
"jshint": ['.jshintrc', '.jshintignore']
}
}
}
These 2 issues are similar: https://github.com/tschaub/grunt-newer/issues/83 https://github.com/tschaub/grunt-newer/issues/32
When using
grunt-jscs
orgrunt-contrib-jshint
, editing your linting rules does not cause your entire source tree to be re-linted unless you rungrunt clean
or manually remove the.cache/
directory. This can lead to mistakenly thinking your source tree is compliant with the linting changes until you run a clean build at a later time.It would be nice if there was an option to
grunt-newer
to tell it to invalidate the entire.cache/
directory ifGruntfile.js
has been modified since the last run. Finding a solution that also works withload-grunt-config
could be tricky.If you're not using
load-grunt-config
, a workaround is (Unix only):