Grunt connect livereload example12/31/2023 ![]() It removes the debug-brk, adds a new one, then immediately bombs out without running a test. 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. It essentially acts like a run task at that point. For the watch and livereload, you need to specify which files to watch, and what tasks to execute in your Gruntfile, again, take a look at this sample Gruntfile. 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. ![]() 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) you still need a separate livereload server, try node-livereload, grunt-contrib-connect or grunt-contrib-watch. files: app/less/ livereload: < > tasks: less.usr/local/bin/node -debug-brk=57906 /usr/local/lib/node_modules/grunt-cli/bin/grunt -gruntfile /Users/project/Gruntfile.js e2e-test Watch for changes to less files, then run the less Grunt task. 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. Ive been staring at my grunt config for a couple of hours now and cant seem to get things up and running. ![]() I have a set of grunt tasks, which start a web server and a set of jasmine testcases via protractor + Selenium. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |