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

[breaking change] JSZip v3: drop node 0.8 support. #270

Merged
merged 1 commit into from Mar 23, 2016

Conversation

Projects
None yet
2 participants
@dduponchel
Collaborator

dduponchel commented Mar 21, 2016

Since nodejs 0.10.26 (npm 1.4.3), the default when doing a npm install --save
is to use caret ranges (^1.2.3). It is now nearly impossible to use
nodejs 0.8 with recent version of libs because of this: if a transitive
dependency uses a caret, we get a "No compatible version found" error.

We can't use Travis to test nodejs 0.8: because of these dependencies,
the npm install phase failed.
From here, nodejs 0.10 still has a lot of users while nodejs 0.8
doesn't even appears on the chart.

[breaking change] drop node 0.8 support.
Since nodejs 0.10.26 (npm 1.4.3), the default when doing a `npm install --save`
is to use caret ranges (`^1.2.3`). It is now nearly impossible to use
nodejs 0.8 with recent version of libs because of this: if a transitive
dependency uses a caret, we get a "No compatible version found" error.

We can't use Travis to test nodejs 0.8: because of these dependencies,
the `npm install` phase failed.
From [here][0], nodejs 0.10 still has a lot of users while nodejs 0.8
doesn't even appears on the chart.

[0]: https://semaphoreci.com/blog/2015/12/15/nodejs-version-usage-in-commercial-projects-2015-edition.html

@Stuk Stuk merged commit 5b59f60 into Stuk:jszip_v3 Mar 23, 2016

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details

@dduponchel dduponchel deleted the dduponchel:drop_node_0.8 branch Mar 24, 2016

@dduponchel dduponchel referenced this pull request Apr 12, 2016

Merged

Release 3.0.0 #278

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