jsHint not working when watching about grunt-contrib-watch HOT 14 CLOSED

Yep confirmed on Windows. Watch will spawn the task but then immediately closes. Will look into a fix shortly. Thanks!

from grunt-contrib-watch.

After further investigation I've found that this works with the latest Grunt v0.4 and watch task. Try installing both using a git url as dependency. Won't be an issue when each are officially released. Thanks!

from grunt-contrib-watch.

Cool. Thanks!

from grunt-contrib-watch.

I installed the latest commit from the grunt devel branch and this bug is still present. Here is my current package.json:

{
  "name": "my-project-name",
  "version": "0.1.0",
  "devDependencies": {
    "grunt": "git://github.com/gruntjs/grunt.git#1f77fef26c564fe74e0b9860f055703649156113",
    "grunt-contrib-jshint": "~0.1.0",
    "grunt-contrib-nodeunit": "~0.1.0",
    "grunt-contrib-sass": "~0.2.1",
    "grunt-contrib-uglify": "~0.1.0",
    "grunt-contrib-watch": "git://github.com/gruntjs/grunt-contrib-watch.git#6360a36871d55a7a500f86e0ddd0fb9cd08f2773"
  }
}

FWIW the first time npm install ended silently for some reason. ( https://github.com/isaacs/npm/issues/2981 )

So I uninstalled this module and ran npm install again which seemed to install the watch module again. But still grunt watch is not reporting any lint errors.

from grunt-contrib-watch.

Hmm I'll check again.

from grunt-contrib-watch.

I have slightly different problem - watching for file changes fires linting on change ev. If linting fails I get classic error message:

Aborted due to warnings.

Problem with it is, that after this error, linting of the file is not restarted. Correcting the file will not initiate relinting affected file. Other files keep linted until first error.

update: not related to original issue, also solved :)

from grunt-contrib-watch.

I updated grunt to the latest version (then) a few days back and it is working fine now. Thanks guys!

from grunt-contrib-watch.

Oh awesome, closing then. :D

from grunt-contrib-watch.

I had the exactly same issue w/ [email protected], after updating to 0.2.0 the problem disappeared :)

from grunt-contrib-watch.

I'm on windows 7 with "grunt": "~0.4.0", "grunt-contrib-watch": "~0.3.1" and it reproduces for me.
jshint when ran in watch, does not report it's results, only have indication that watch is triggered, but no results, unless jshint passes successfully.

from grunt-contrib-watch.

I am getting the exact same result as swar30 when I run the grunt task from WebStorm. If I just run it from command line, it works fine.

from grunt-contrib-watch.

Have this issue as well, where it works the first time, maybe a second time (sometimes), but subsequent watches do not trigger.

Using grunt-contrib-watch 0.4.4, grunt-contrib-jshint 0.6.0, with grunt 0.4.1.

Looks like an issue with nospawn: true.

from grunt-contrib-watch.

Hey Im having the same issue in windows. Is there any updates on this?

Im using <grunt 0.4.1> <"grunt-contrib-jshint": "~0.6.0"> <"grunt-contrib-watch": "~0.5.1">

from grunt-contrib-watch.

Your issue is likely something different the original poster's issue. Please open a new issue with a description of the error you're experiencing, the portion of your watch config. Also try debugging using grunt watch --verbose or grunt watch --stack to ensure something isn't mistakenly configured. Thanks!

from grunt-contrib-watch.