search

duojs / duo

A next-generation package manager for the front-end
3.42k stars 118 forks source link

add the oldest node version supported #480

Closed Mouvedia closed 8 years ago

Mouvedia commented 9 years ago

duo doesn't support node 0.10.33 cf my comment here.

You should add your requirements in the README.

stephenmathieson commented 9 years ago

yes, we dropped support for 0.10. supporting old versions of node is more work than it's worth.

I'm +1 to mentioning this in the readme and/or using the engines field in our package.json.

dominicbarnes commented 9 years ago

Just to be clear, while we don't support node 0.10 "natively", you can easily run Duo using a transpiler. The bare minimum is gnode, since you only need generators, but you can also use Babel if your codebase is using more ES6.

However, the transpiling comes at a price. While not benchmarked, the tests take roughly twice as long to run. There's no reason for avoid upgrading to node 0.12 at this point, so I'd recommend that if possible.

On Wed, Jul 8, 2015, 8:56 AM Stephen Mathieson notifications@github.com wrote:

yes, we dropped support for 0.10. supporting old versions of node is more work than it's worth.

I'm +1 to mentioning this in the readme and/or using the engines field in our package.json.

— Reply to this email directly or view it on GitHub https://github.com/duojs/duo/issues/480#issuecomment-119633906.

dominicbarnes commented 9 years ago

We do run our tests using node 0.10 + gnode, and that likely won't change soon.

On Wed, Jul 8, 2015, 9:14 AM Dominic Barnes dominic@dbarnes.info wrote:

Just to be clear, while we don't support node 0.10 "natively", you can easily run Duo using a transpiler. The bare minimum is gnode, since you only need generators, but you can also use Babel if your codebase is using more ES6.

However, the transpiling comes at a price. While not benchmarked, the tests take roughly twice as long to run. There's no reason for avoid upgrading to node 0.12 at this point, so I'd recommend that if possible.

On Wed, Jul 8, 2015, 8:56 AM Stephen Mathieson notifications@github.com wrote:

yes, we dropped support for 0.10. supporting old versions of node is more work than it's worth.

I'm +1 to mentioning this in the readme and/or using the engines field in our package.json.

— Reply to this email directly or view it on GitHub https://github.com/duojs/duo/issues/480#issuecomment-119633906.