npm install chromy fails about chromy HOT 12 CLOSED

latest version appears to be ^0.1.2

but on Chromy package.json it is ^0.1.3

I downloaded the zip and changed to 0.1.2 and ran npm install

from chromy.

@dotneet : is this something going to be fixed soon?

from chromy.

Yeah I'm experiencing the same problem. Using yarn I can interactively choose 0.1.2 but that doesn't work on the CI system.

from chromy.

Sorry, I forgot to publish async-await-chain.
I now published 0.1.3. please npm install again.

from chromy.

Should be good to go now, @NimaSoroush can you verify?

from chromy.

@dotneet @Primajin : Works fine now. Thanks

from chromy.

Hi @dotneet : what is the node version requirement to run chromy?

from chromy.

Hi @NimaSoroush
Chromy requires node 7.6 or later because of using async/await keyword.

from chromy.

Hi @dotneet,
is that ok if we run add compatibility to elder version through babel?
I wanted to run chromy in one of out pipelines which uses node6.9 and we can't update node version there.

from chromy.

Basically I agree with this suggestion.
But I can't imagine how you do it.
Could you tell me that?

from chromy.

Hi @dotneet:

Just created this PR to discuss how we would approach this. #19

The same change should apply to https://github.com/OnetapInc/async-chain-proxy too

already tested this locally and works as expected with node 6.9 and npm 4.

from chromy.

Thanks!
I understood your approach.
I commented on PR!

from chromy.