-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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 0.12 support justifies a new version #1378
Comments
…-curl dependency You'll probably receive a Karma warning for node.js but things are fine, see: karma-runner/karma#1378
👍 please publish to npm! |
👍 |
@maksimr @vojtajina is there any specific reason no new release for this has been cut yet? |
+1 |
@dignifiedquire build script is broken :( Now project lead @zzo |
Ah right, that explains it, @zzo any chance we can get that script running again, and or that you can publish a new version/give some of us the ability to manually publish a new version in the meantime? |
Sorry guys am on it - having problems with the auto-release system so I'll On Tue, May 5, 2015 at 7:01 AM, nmccready [email protected] wrote:
|
@zzo thanks for the reply. Not sure if this is related or not (requires a new issue). master is hanging against io.js 1.8.1 and likely (2.0.0). |
+1 for Node 0.12 |
Anyone have any idea why this is? Sounds like a new issue. On Tue, May 5, 2015 at 7:24 AM, nmccready [email protected] wrote:
|
Can we help somehow? If I'm not mistaken there new release isn't public yet, but if there is anything that we could help with to make it happen please let us know @zzo ! |
0.12.33 should be on npm allowing for node 0.12 and iojs. Please comment and or reopen if it does not work. |
Works for me, thank you very much! :) |
The NPM package v0.12.31 contains the the following in its package.json:
This causes a warning to be shown whenever karma is installed on node >0.10
Meanwhile support for the node 0.12 is already fixed in the github repo:
Please increment the version number and publish the new version to NPM as soon as possible. The current state with the warning looks kind of scary. Maybe not top prio but an easy fix. ;)
The text was updated successfully, but these errors were encountered: