I also tried removing the old node -debug-brk and adding one for the grunt task using a solution I saw suggested, but this did not work.
use the -force option forceOff, <- turn the -force OFF connect:livereload. It essentially acts like a run task at that point. If you use this option like this for example grunt server -force. After setting up our configuration object, running grunt concat, grunt concat:dist, or grunt build in the shell in the project root will all do the same thing: concatenate all scripts in the scripts sub-directory into a single script called main.js. Should I switch to another port? Is the debugger using 9000?Īdding process.execArgv = to the top of the gruntfile allows the process to complete without a debugging conflict, but will not stop at any breakpoints or allow any actual debugging. you still need a separate livereload server, try node-livereload, grunt-contrib-connect or grunt-contrib-watch. Started connect web server on Running "protractor:e2e" (protractor) taskĪt exports._errnoException (util.js:746:11)Īt Agent.Server._listen2 (net.js:1146:14)Īt Object.start (_debugger_agent.js:20:9) Open your custom.css or less file for example then change something then save, here youll see in grunt. usr/local/bin/node -debug-brk=57906 /usr/local/lib/node_modules/grunt-cli/bin/grunt -gruntfile /Users/project/Gruntfile.js e2e-test LiveReload monitors changes in the file system. I'm getting an error as if it's already running The problem is, when I select to run the grunt test in debug mode. I have a set of grunt tasks, which start a web server and a set of jasmine testcases via protractor + Selenium.
0 kommentar(er)
