I've seen #206 and it's wishlist of features for a v1 release, but this library has had over 300,000 downloads in the last month according to npm's website, plus however many bower users too.
The semver spec says:
How do I know when to release 1.0.0?
If your software is being used in production, it should probably already be 1.0.0
It's definitely being used in production, so how about it?
achingbrain
All 3 comments
I agree. If we can get #50 figured out (being worked on by @nickuraltsev AFAIK) as well as #257 we will release a 1.0.
mzabriskie
on 31 Aug 2016
Not sure those issues would stop me from releasing a v1 馃槈 - cancelling Promises is a problem bigger than this library and IMHO the README.md is comprehensive enough to stand in for a documentation website for the time being.
The reason I bring it up is I have a project that has a few different versions of axios in the dependency tree - 0.13, 0.14, etc with no observed functional difference between them - the multiple versions play havoc when trying to stub them in our testing, set global defaults, etc. If v1 were to be released they could all resolve to the same version (e.g. ^1.0.0) which would make life much simpler.
achingbrain
on 31 Aug 2016
Just stumbled across this after wondering how a project that has been around and so heavily used for over four years has not made it to 1.0.0 yet ;-)
WillGibson
on 6 Mar 2019
Related issues
Spartano
路
3Comments
c0debreaker
路
3Comments
samayo
路
3Comments
ildella
路
3Comments
tbaustin
路
3Comments
Most helpful comment
Just stumbled across this after wondering how a project that has been around and so heavily used for over four years has not made it to
1.0.0yet ;-)