Use same version of coffeescript as bigmaven

[roblevintennis]

No description provided.

[roblevintennis]

I could not get the unit tests to run. I tried:
npm install -g nodeunit
npm install -g nodeunit@0.9.0 (per https://github.com/conversation/ShareJS/pull/16/files#diff-04c6e90faac2675aa89e2176d2eec7d8R51) but it wouldn't install.

For global nodeunit installation I had tried nodeunit test and cake test etc. etc. but was not able to get them to run. I'd be curious if anyone has done so in last few years ;)

If either of you knows how to run the suite I will, but otherwise onwards

[naganowl]

This should be a logical change so as long as npm install is successful this is good.

An additional check would be to point to this branch and observe that the test suite is green before merging this in.

[naganowl]

Given that this matches what we've been using, this should be good!

[roblevintennis]

Thanks Alan. Re

An additional check would be to point to this branch and observe that the test suite is green before merging this in.

I think that's a great idea Alan, and we'll need a PR to update our reference back anyway, so doing that should give us more confidence: https://github.com/mavenlink/mavenlink/pull/16795

I'm assuming this will go like:

1. Ensure that bigmaven goes green
2. Merge this
3. Point back to eco#master from bigmaven, re-run yarn install and check in the update
4. Ensure that again goes green
5. Merge that in to bigmaven

[naganowl]

Yep, just like if this were a mavenlink-js change!

[roblevintennis]

I was led to doing all this from seeing the CI issue off bigmaven which as you can see points back to this compiler.js script

[roblevintennis]

Ok, since https://github.com/mavenlink/mavenlink/pull/16795 is CI green, I think we're all good. Merging.