Skip to content
This repository has been archived by the owner on Jan 4, 2018. It is now read-only.

Update required node and npm versions #85

Closed
wants to merge 2 commits into from
Closed

Update required node and npm versions #85

wants to merge 2 commits into from

Conversation

sirreal
Copy link

@sirreal sirreal commented Nov 9, 2017

This PR updates the documentation to support for node >=4 and npm >=2.14.2.

The current version of mocha pulls in dependencies which use arrow functions which fail in earlier versions of node.

See https://travis-ci.org/sirreal/mocha/builds/299600162, where I forked mocha and added tests for earlier versions.

If node 4 is required, it seems to make sense to report npm@2.14.2 as the minimum version since that is what shipped with node v4.

Just update the documentation to remove support for node `<4`.

The current version of `mocha` pulls in dependencies which use arrow functions which fail in earlier versions of node.

See https://travis-ci.org/sirreal/mocha/builds/299600162, where I forked `mocha` and added tests for earlier versions.
If node v4 is required, it's silly to require npm@1.
@jsf-clabot
Copy link

jsf-clabot commented Nov 9, 2017

CLA assistant check
Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

@ScottFreeCode
Copy link

Good catch, thanks!

@mochajs/core do we want to hold off on this till we resolve mochajs/mocha#3073?

We should also make a note that, after this repo is rolled into the other (mochajs/mocha#2987), this ought to be automatically generated from package.json just as the help-documentation output in the Usage section ought to be automatically generated from mocha --help.

@boneskull
Copy link
Member

@ScottFreeCode I'm just manually pulling this stuff in

@boneskull
Copy link
Member

@sirreal Can you please sign the CLA?

@boneskull
Copy link
Member

merging this with mochajs/mocha#3123 anyway

@boneskull boneskull closed this Dec 9, 2017
@sirreal
Copy link
Author

sirreal commented Dec 9, 2017

Can you please sign the CLA?

I've been hoping to but actually can't. I have a preexisting agreement with an organization. My organization has been in touch with the JSF about the CLA but as far as I know there's been no response, which is what I'm waiting on. 🤷‍♂️

@boneskull
Copy link
Member

cc @krisborchers can you help?

@boneskull
Copy link
Member

errr @kborchers

@JSFOwner
Copy link

@sirreal @boneskull We were contacted by your org on November 12 and I responded on November 13 with details around how our CLA works and a potential option for corporate CLA but have not heard back from them.

@sirreal
Copy link
Author

sirreal commented Dec 11, 2017

Thanks for the info, I'll check on my end to try to get some movement.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants