Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Windows users cannot run CJSE build task #119
I rebased my code for #109 and now I cannot run the npm scripts because somebody changed the commands to using
That is not really in the spirit of cross-platform code and unnecessary as there are many node.js based build runners.
referenced this issue
Jul 23, 2013
This needs a real decision by a core member.
Until then I'll spin up a VM, but as said a (modern) node.js application shouldn't have to depend on OS specific tooling.
If disagree on this I could also commit a Vagrant file and cookbook for easy testing on a headless Ubuntu on VirtualBox.
Edit: I have the Vagrant file ready, but it is a bit of a nuclear option imho. If the project embraces node.js and welcomes contributions it shouldn't require a few gigabyte of Linux, Ruby, Vagrant, Chef and VirtualBox :)
I'm wondering if its related more to Git Bash than Jake. I need to try it on a separate VM when I get a second. The thing is, it is definitely still checking code coverage because you will get a non zero exit code if the coverage drops below the threshold...it's just not outputting the report.
I suppose in
I tried it also with commonjs-everywhere 0.9.4.
Getting the verbose output...
The command executed was the following: