-
Notifications
You must be signed in to change notification settings - Fork 779
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QUnit 2.7 claims compatibility with Node 4, but fails #1321
Comments
This was discussed in #1299, and QUnits policy roughly matches Ember CLI’s (only supporting supported node versions). The engines field should have been updated in that PR though... |
that is quite unfortunate... Do we need to pin it then in ember-qunit? |
We should pin in ember-qunit (IIRC ember-cli-qunit doesn’t have a qunit for directly any more), then release a major I guess (need to drop Node 4 and ember-cli < 2.13 over there). |
@rwjblue yep, that seems like the right thing to do to me. see emberjs/ember-qunit#353 |
Oops, closed prematurely. Need to update the Line 100 in ed88074
|
Some of our CI systems are still running on Node 4 and the
qunit
npm package claims that it's still compatible with it:https://github.com/qunitjs/qunit/blob/2.7.0/package.json#L100
Unfortunately
qunit
has a dependency onsane@4
though, which is Node 6+. It seems that this dependency bump was introduced without a change to the Node requirements of QUnit 🤔As our CI will try to install the latest
qunit
, it will try to installsane@4
now and fail:/cc @trentmwillis @stefanpenner
The text was updated successfully, but these errors were encountered: