On Windows, I have the following .cmd file:
.\node_modules\.bin\coffee .\lib\cli --html="index.htm" --whichBuild="configs/whichBuild.xml" %*
That is:
- I call
.\node_modules\.bin\coffee.cmd - Telling it to execute
.\lib\cli.coffee - Passing it parameters
--html="index.htm" --whichBuild="configs/whichBuild.xml" - And also passing it any parameters the user gave me on the command line.
On Mac, I've got no idea what to do. node.exe and coffee.cmd aren't going to be around. How are these things accomplished?
I want something easy I can tell our build-guy "run myCommand arg1 arg2 and it'll work." I have that on Windows, but on Mac I'm clueless.
Also of note: one of the features of my Windows approach that is nice is our build-guy doesn't have to install node or npm or coffee-script or anything. He just grabs a directory from source control, which has node.exe, coffee.cmd, etc. all packaged up. A similar feature for Mac would be highly desired.