![]() ![]() Again, almost everything is preconfigured for you only the Program must be chosen manually. Select Tools > File Watchers node in the tree view on the left (you can search for file watchers, to find it quicker) and click on the "plus" icon in the top right corner to add a new file watcher, based on CoffeeScript template. You will first need to configure a CoffeeScript file watcher in the Settings dialog. It turned out that WebStorm's file watchers were the right way to go. Not only was that much less convenient (having to manually start Node from command line every time), the mapping to CoffeeScript source was also mismatched, which made the approach almost useless. My next attempt was starting the Node interpreter directly and attaching to it from WebStorm. Even though Grunt can run CoffeeScript scripts directly, WebStorm will report errors if you set a CoffeeScript Gruntfile in your debug configuration. If your Gruntfile is written in CoffeeScript, you're not done yet. You can now set a couple of breakpoints and start debugging using the Run menu or the Debug tool window (the latter will open automatically once you start debugging, if you have it closed). If you have written your Grunt script in JavaScript, then that's all you need to do. Optionally you can also set the Tasks to run if you want to debug anything else than default. The only things left for you to fill in are the configuration Name (up to you) and the path to the Gruntfile you want to the debug.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |