-
Notifications
You must be signed in to change notification settings - Fork 34
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
Support for IO.JS #423
Comments
Will need to look through things. But yeah. |
I've heard that a system alias should be enough, linking to Especially nodejs/node#429 (comment) is stating that the user bin will also stay with So, the remaining work here would be to check whether io.js is fully working with mimosa. I would love to help you testing it on my local linux machine. Btw, NVM will also adopt io.js: |
+1 |
My plan is to validate .12 and io with |
BTW, https://github.com/dbashford/mimosa/blob/2point4/.travis.yml So the travis config currently runs all the tests in iojs. I still have a lot of tests to write, though.
|
FWIW, io.js will not see any new major releases while Node.js 4.0.0 (the first converged release) is out. |
FWIW, the 2point4 branch of this works with |
Good timing! I just got a new web project and may use mimosa again. Thanks @dbashford! |
It won't be the full 3.0 I was hoping to release, where I stalled at way back in ~March is where the codebase remains for now, but it may be worth releasing 3.0 just to get it out. I've just had no time to devote to it and diving back in gets a little harder the longer it takes me to get back. |
Hi @dbashford , is Mimosa still active? |
Afraid not. Haven't done anything with it in a long time. |
Will you add support for https://iojs.org/ ?
You have some places that are hardcoded with
node
.The text was updated successfully, but these errors were encountered: