Support for IO.JS

[Anachron]

Will you add support for https://iojs.org/ ?
You have some places that are hardcoded with node.

[dbashford]

Will need to look through things. But yeah.

[Anachron]

I've heard that a system alias should be enough, linking to iojs instead of node.
Discussion: nodejs/node#429

Especially nodejs/node#429 (comment) is stating that the user bin will also stay with node.

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:
nvm-sh/nvm#590

[dcartertwo]

+1

[dbashford]

My plan is to validate .12 and io with 3.0. The tests will help with that.

[dbashford]

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.

language: node_js
node_js:
  - 'iojs'
  - '0.12'
  - '0.10'

[mgol]

FWIW, io.js will not see any new major releases while Node.js 4.0.0 (the first converged release) is out.

[dbashford]

FWIW, the 2point4 branch of this works with v4.0.0. Yesterday I added v4.0.0 to the travis build that is running on that branch. I may just release mimosa 3.0 out of that branch here in the next few days.

[Anachron]

Good timing! I just got a new web project and may use mimosa again.

Thanks @dbashford!

[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.

[stela5]

I've just had no time to devote to it

Hi @dbashford , is Mimosa still active?

[dbashford]

Afraid not. Haven't done anything with it in a long time.