I am using WebStorm to run a grunt task. The debugger successfully stops at the breakpoint in the Gruntfile.js file, but not in my task file.

In the Gruntfile.js I register a task like this:

grunt.initConfig({
  ... configuration ...
});    
grunt.registerTask('myTask', ['mocha:myTask']);

When I set a breakpoint in the corresponding js file for the test 'myTask' it doesn't stop. How can I debug also the grunt tests?

--- UPDATE ---------------------------------------

so i tried all of your possible solutions, but it does not solve my problem!

I am able to debug the grunt script itself, this is where the debugger actually stops (either in WebStorm or node-inspector). Also a breakpoint in Gruntfile.js is working.

The problem is, that I am not able to debug the actual Grunt task itself, registered with grunt like this: grunt.registerTask('myTask', ['mocha:myTask']);

I am also able to debug the mocha test itself. But I want to debug a mocha test called from grunt task runner. Any ideas?

I am using WebStorm to run a grunt task. The debugger successfully stops at the breakpoint in the Gruntfile.js file, but not in my task file.

In the Gruntfile.js I register a task like this:

grunt.initConfig({
  ... configuration ...
});    
grunt.registerTask('myTask', ['mocha:myTask']);

When I set a breakpoint in the corresponding js file for the test 'myTask' it doesn't stop. How can I debug also the grunt tests?

--- UPDATE ---------------------------------------

so i tried all of your possible solutions, but it does not solve my problem!

I am able to debug the grunt script itself, this is where the debugger actually stops (either in WebStorm or node-inspector). Also a breakpoint in Gruntfile.js is working.

The problem is, that I am not able to debug the actual Grunt task itself, registered with grunt like this: grunt.registerTask('myTask', ['mocha:myTask']);

I am also able to debug the mocha test itself. But I want to debug a mocha test called from grunt task runner. Any ideas?

• javascript
• node.js
• gruntjs
• webstorm

• How are you loading the task? – Kara Brightwell Commented Sep 25, 2014 at 15:41
• Maybe you can use this to help find where things are stopping: grunt.registerTask('debug', function(arg){ grunt.log.writeln(arg); }); Call the debug task and pass it a string. That string will be outputted to the console. – MBielski Commented Sep 25, 2014 at 15:42
• @MattBrennan I have updated my question... Do you mean that? – electronix384128 Commented Sep 25, 2014 at 18:03
• @MBielski yes, i can debug that, no problem. but how can i actually debug the 'loopmocha:myTask'? – electronix384128 Commented Sep 25, 2014 at 18:07
• 1 Have you tried using a debugger; statement in your task file? I've found that often fixes issues like this in webstorm. – dc5 Commented Sep 25, 2014 at 18:23

4 Answers 4

To run grunt task in debug, you need to pass the grunt task script to node-inspector:

node-debug $(Path \AppData\Roaming\npm\node_modules\grunt-cli\bin\grunt) task

Put a debugger; line in your task. node-inspector will then open a browser with debugging tools.

This link help you how its work grunt-node-inspector

Example: ChrisWren/grunt-node-inspector

Source: Stackoverflow Question

Finally I am able to debug my mocha tasks! Thanks for all your answers and ments, but unfortunately I have to select my own answer, because that is the only one that worked for me.

Thanks to this video I found out what I was missing: http://vimeo./97561531

Basically it was two things:

1. Add a "debug-brk" option to grunt's mocha configuration:

   grunt.initConfig({
       ...
           "options": {
               "mocha": {
                   ...
                   "debug-brk": (grunt.option('debug-brk')) ? "" : 0
               }
           }
   }
   

2. Configure WebStorm's Debug Configuration like this:

If you happen to use the WebStorm IDE you can set up a task and then either run or debug it.

You can see the configuration for the mand grunt jasmine_node_no_coverage in the screenshot. Please note that I installed grunt globally.

Try out grunt-debug-task.

Its similar to node debugger. Just run the grunt debug taskname

I tried it out. It breaks sometimes but seems to work.