Project dead?

[youurayy]

Is the project dead? Are new maintainers sought?

• 97 open pull requests
• 411 open issues

[likern]

And no commits in master since September. No plans to support HTTP2 yet.

[atrauzzi]

Yeah, kind of wondering the same thing lately...

[emilyemorehouse]

It's not dead, I just haven't been able to personally do as much on the project lately. We had a big issue with fixing configurations, which introduced breaking changes, that have halted things until that gets fixed.

So yes, if there are people willing to step up and help as maintainers, I welcome them!

[youurayy]

@emilyemorehouse maybe it would be a good idea to advertise that in the README.md, I'm sure there are folks who want to help.

[rogeriopvl]

@emilyemorehouse I would be glad to help out as a maintainer

[43081j]

Haven't used the project before admittedly but usually found digging around github, so happy to have a read through some PRs in my spare time.

What would be super nice is a new version which uses ES modules 🙊

[iidrees]

Hi @emilyemorehouse, I would love to help out.

[ironicnet]

I think that doing triage or labeling the issues would help the new volunteers to know where to start...

[hugomd]

I’d be keen on helping out, whether it’s triaging, actively contributing, or anything else 🤙

[lnghrdntcr]

@emilyemorehouse I'd love to help! Probably would be nice to have a some sort of tags (like, 'for beginners' or similar) on the issues in order to encourage contributors!

[rajasekarm]

I’m using axios for more than a year. I can help in fixing bugs.

[gkarwchan]

I would love to contribute. I used axios in 4 projects so far, and it is my first choice always.

[GlebkaF]

I could help, just tell me what to start with :)

I guess we should start with roadmap to stable 1.0.0 release, then split in into issues with "help wanted" label.

[eranshapira]

count me in.

[simsim0709]

As the heavy user of axios, it would be great if I can help out. :)

[3sanket3]

I don't have much contribution history but I use axios in projects. I will happy to help.

[kofoworola]

As an axios junkie, i'd love to help however i can

[ellepereira]

@mzabriskie @emilyemorehouse please let me know how we can help!

[cdcasey]

I would love to help.

[wlepinski]

I would love to help as well.

[nickstew]

I'd be happy to assist in maintaining this project. I've been using it for years and would be happy to lend a hand, @emilyemorehouse. ❤️

[bmacher]

I would help aswell. :)

[zazapeta]

I get so much fun to use axios in a dozen of project. I'd be enchanted with helping a bit 🌞

[nolleto]

I would like to help too 😄

[atishaybaid]

I would like to contribute and maintain ,let me know where to start

[varijkapil13]

I am using axios since along time and in multiple projects,, I would love to help any way possible

[KartikJha]

Would love to help.

[bipinct]

will be my pleasure to contribute to axios

[mowatermelon]

I would love to help as well.

[jasonsaayman]

I am also willing to get involved, we use axios in a number of extremely critical projects. It would be terrible if axios were to not be supported in the future.

[igorshubovych]

@emilyemorehouse,
@mzabriskie,
@nickuraltsev,
@rubennorte,

You are the owners in Axios.

Could you please discuss adding more collaborators to the project so it gets unblocked?

[Sequoia]

This issue having been open for 4 months now, I'm inclined to agree with the complainers here at this point. Good stewardship of this project would look like either:

a) picking from among the many willing people to add more contributors, or
b) marking the project as archived to make maintenance intentions clear & allowing people to move on to next steps or
c) maintainers step back in to continue active maintenance

Maintainers: it would be a great service to the community of users if you would please pick one of the above option so those interested in maintaining this project can move forward. Archiving is perfectly acceptable 👍

[mapleeit]

I saw that @emilyemorehouse merged some PRs yesterday. So it seems there are still somebody working on this repo. That's really great.

So did you guys finish with the "big configuration issue"? When will the next version be released?

Thanks for your efforts.

[leslie-alldridge]

I love axios, keen to help however I can

[robmcguinness]

🙏 https://github.com/axios/axios/releases/tag/v0.19.0

[igorshubovych]

Hats off to @emilyemorehouse for making a release.
I hope there will be a possibility to do regular releases soon.

[jphilipstevens]

@emilyemorehouse

I would also like to.help out. At my work we use Axios quite a bit and I'm more than willing to spend time on this project

[ouraios]

ping @rubennorte @mzabriskie @emilyemorehouse @nickuraltsev

Lots of people using your amazing package are waiting from you to take some actions to take some more hands to help you !

And if you dont have time to do those actions then maybe you could at least label this package as dead ?

Maybe setting up a patreon could help you to be motivated to start working on it again ?

[akx]

I wouldn't mind helping either, e.g. in a triage role (https://github.blog/changelog/2019-05-23-triage-and-maintain-roles-beta/) :)

[thexpand]

I think that was a begged release, because I don't see any activity after the latest 0.19.0 release.
Such a shame for such an awesome HTTP client.

[snowdream]

Is there any plan to add HTTP/2 support for node.js? #1175

[igorgue]

Looks like a pretty alive project to me...

[akx]

Looks like a pretty alive project to me...

There was an entirely quiet period from May to September, if you look closely.

Either way I'm happy momentum is picking up again. :)

[unguul]

With a reported usage of 1.8m you'd expect this package to receive some kind of financial backing. I see no patreon, opencollective, tidelift or [insert income sources here] mentioned anywhere. I created #2493 for follow up.

[viT-1]

What about esm version?
#1879

[BrunnerLivio]

The Googleapis organization has started a new project called gaxios

The reason why from issue googleapis/gaxios#81:

We were originally using axios, but created this for a few reasons:

• Axios has been relatively unmaintained recently
• It didn't support proxy support out of the box
• It didn't support retry out of the box
• It duplicated a lot of client side logic we just didn't need here

Axios is a great library, but we wanted something built on the much lighter node-fetch. Hope this helps!

The motivation behind Googleapis team is understandable, though I feel like it is not a good idea to create a new library which is so similar {insert xkcd comic}. May we can find common ground here and just let it be one “Axios”? cc @JustinBeckwith

[chinesedfan]

Share a personal story and some news for users in this thread,

• I noticed the situation of axios like you guys in Feb 2019 and triaged about 30 issues+pulls.
• Got no responses from the maintainers and felt a little disappointed. But still kept an eye on it.
• Luckily, I was invited as a collaborator in Dec 2019. That started my issue killer time. Total issues have decreased from ~600 to less than 300 now.

I created a plan for the next release. See https://github.com/axios/axios/projects/4. I know there are still some problems in axios, but I hope we can fix those hottest first.

I don't need your words to pay too much time on it, but would someone mind helping review those features when you are free, to make the next release better?

[dpikt]

@chinesedfan that's great news, glad to hear things are moving! Question, since you're now a collaborator- have plans/timeline coalesced around a 1.0 release? Or will upcoming releases all be 0.x for the time being?

Apologies in advance if this has been answered in a different thread.

[jasonsaayman]

Hi,

I think that the v1.0 release as it is currently pinned is so out of date with what it was trying to achieve that I almost want to say its technical debt. The goals of v1.0 should be clearly laid out and evaluated as to what is most important to the community.

I think we should be looking towards stability more than anything else with proper regression testing. Axios needs to also have a stable release strategy that should be locked down in a v1.0 with a more structured pre-release with testing strategy.

I will endeavour to try get a new v1.0 project up with issues etc. very soon.

[Ryuno-Ki]

Given that the maintenance question seem to be solved by now … can we close this issue/lock it?

[jasonsaayman]

Closing for now, please watch projects to see new versions and proposed road map for axios.