-
Notifications
You must be signed in to change notification settings - Fork 452
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
Node.js 4 support #36
Comments
I've changed our test cases a little bit. We can't target But I don't know how to separate test cases for different node versions. @kulshekhar, any thoughts? |
The way I look at it, node 4.x will stop being maintained in about 5 months, So I don't see any point in supporting it. |
In that case, it might be helpful to update the README with the status of support for various versions (the latest for 4 and 6 each?) btw, this can get complicated very fast. I spent a few hours yesterday all because some tests were failing on 6.6 and on 6.3. If this is the case between 6.x versions, I shudder to think what's in store if we are going to support 4.x 😰 |
Ok, build on travis was failed due to not latest I guess we have to show status for different versions of node and will try to find out how it could be accomplished with travis. |
@Igmat Is this good to publish? Maybe node 4 can be removed from the |
@kulshekhar, I've already published it. And I guess we could close this issue. |
Working on issue #35 I've realized that our package doesn't support Node.js 4 (at least it doesn't correctly tested under this version). But Jest supports it, so we have to provide our users with such compatibility.
The text was updated successfully, but these errors were encountered: