Skip to content
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

Closed
mischkl opened this issue Apr 21, 2015 · 14 comments
Closed

Node 0.12 support justifies a new version #1378

mischkl opened this issue Apr 21, 2015 · 14 comments

Comments

@mischkl
Copy link

mischkl commented Apr 21, 2015

The NPM package v0.12.31 contains the the following in its package.json:

  "engines": {
    "node": "~0.8 || ~0.10"
  },

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:

  "engines": {
    "node": ">=0.8 <=0.12",
    "iojs": "~1"
  },

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. ;)

bramcordie added a commit to cultuurnet/udb3-angular that referenced this issue Apr 22, 2015
…-curl dependency

You'll probably receive a Karma warning for node.js but things are fine, see: karma-runner/karma#1378
@vvakame
Copy link

vvakame commented May 3, 2015

👍 please publish to npm!

@lacolaco
Copy link

lacolaco commented May 3, 2015

👍

@dignifiedquire
Copy link
Member

@maksimr @vojtajina is there any specific reason no new release for this has been cut yet?

@rfink
Copy link

rfink commented May 3, 2015

+1

@maksimr
Copy link
Contributor

maksimr commented May 5, 2015

@dignifiedquire build script is broken :(
I don't have permissions publish changes to npm manually

Now project lead @zzo

@dignifiedquire
Copy link
Member

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?

@nmccready
Copy link

bueller

@zzo
Copy link
Contributor

zzo commented May 5, 2015

Sorry guys am on it - having problems with the auto-release system so I'll
try to release this one manually - I'm sure nothing will go wrong :)
thanks,
Mark

On Tue, May 5, 2015 at 7:01 AM, nmccready [email protected] wrote:

[image: bueller]
https://cloud.githubusercontent.com/assets/583593/7474175/a70f6a52-f30d-11e4-80e8-b9dd78d4f257.gif


Reply to this email directly or view it on GitHub
#1378 (comment).

@nmccready
Copy link

@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).

@demisx
Copy link

demisx commented May 5, 2015

+1 for Node 0.12

@zzo
Copy link
Contributor

zzo commented May 5, 2015

Anyone have any idea why this is? Sounds like a new issue.
thanks!
Mark

On Tue, May 5, 2015 at 7:24 AM, nmccready [email protected] wrote:

@zzo https://github.com/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).


Reply to this email directly or view it on GitHub
#1378 (comment).

@noherczeg
Copy link

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 !

@dignifiedquire
Copy link
Member

0.12.33 should be on npm allowing for node 0.12 and iojs. Please comment and or reopen if it does not work.

@noherczeg
Copy link

Works for me, thank you very much! :)

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

No branches or pull requests

10 participants