There are two places where setup for Grunt is described: printed pages 50 and 72. Both show
$ mkdir coffee-tasks $ cd coffee-tasks $ npm init
although the two project directories should be jQuery and Node. This causes a certain amount of confusion.
The more serious problem seems to be a conflict with the semantics of src in the project directory structure.
Why would the coffee processing output of Gruntfile.coffee be called src? What controls this? Why isn’t it Gruntfile.js?
$ grunt Running "coffee:compile" (coffee) task >> 0 files created. Running "coffee:cwd" (coffee) task Warning: Unable to read "src/" file (Error code: EISDIR). Use --force to continue. Aborted due to warnings.
Furthermore, if you use grunt - -force grunt works as expected for everything except coffeeScript files in src/. I.e., it processes eco files and places the results in compiled/, it uses watch to look for changes, and it discovers changes to src/*.coffee files, but (silently) fails to write anything to compiled/.
... >> File "src/card.coffee" changed. Running "coffee:compile" (coffee) task >> 0 files created. Done, without errors. Completed in 0.523s at Tue Jul 28 2015 09:03:26 GMT-0500 (CDT) - Waiting...
Any suggestions? What am I missing?