Axios: Project dead?

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

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

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!

@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.

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

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 🙊

Hi @emilyemorehouse, I would love to help out.

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

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

@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!

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

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

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.

count me in.

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

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

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

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

I would love to help.

I would love to help as well.

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. :heart:

I would help aswell. :)

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

I would like to help too 😄

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

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

Would love to help.

will be my pleasure to contribute to axios

I would love to help as well.

Would love to start contributing, been using it for a year so far for all of my projects and I want to help to keep it healthy.

Some type of guidance on where to start would be appreciated though!

Would love to help as I have used axios extensively.

😭 y'all are AWESOME.

To anyone who wants to help, here are a few ideas I have:

• Triage issues: I recently added issue templates to help auto-tag issues (and filter out actual bugs vs usage issues). There's _a lot_ of noise for this project and I spend the majority of my time trying to filter through issues and wind up closing most of them with a simple "This doesn't seem like an Axios bug (many I can't even duplicate), I think X may be your issue, feel free to post on Gitter or Stack Overflow for help debugging your code". If you find a real bug that doesn't have example code, providing example code is a HUGE help. Bonus points if it's as simple as copy/pasting into Runkit with calls to an example API like JSON Placeholder.
• PR Review: Not quite as noisy as issues, but this can still be a lot to go through. I really appreciate people who tag me in PRs that have high priority/fix known issues. Feel free to ping me if I don't respond after a few days. Currently, the focus is definitely getting things stable before focusing on new features or 1.0.0.
• CI: Our CI is finicky - we often hit weird edge cases or issues that cause CI to break and that slows up the whole procress. If we have a broken master branch, I can't release, plain and simple. So if you ever see that master is failing (or PRs are failing for issues not caused by the PR), any help there is massively appreciated.

I'm happy to give anyone access as needed. The only thing I'd like to hold onto is acting as the release manager to ensure consistency.

I plan on adding this info to the contributing doc along with my response templates for others to use and guidelines for how issues should be labeled, etc.

@emilyemorehouse I posted a request for help on reddit (https://www.reddit.com/r/javascript/comments/an94xq/axios_needs_maintainers/) - as you can see, your work has a lot of fans. I look forward to start contributing and once again- thank you.

@emilyemorehouse would love to help out.

@emilyemorehouse I would love to help out

@emilyemorehouse I too would love to help!

It seems like a contradiction.

• Without contributions, @emilyemorehouse can't distinguish helpful people and grant permissions.
• Without permissions, people usually won't start to contribute.

I suggest everyone try to subscribe as code helpers first. If we can persist in triaging issues or sending pull requests, @emilyemorehouse will be more glad to see. And one day, you will be a maintainer naturally.

I use axios and am not currently concerned about lack of ongoing development (tools typically don't blow up the moment a maintainer steps away), but if anyone is really raring to go & wants to start merging PRs, note that this is an open source project and that there's no cost (besides time) to forking & start reviewing and merging PRs to your fork. This can be a natural progression in the life of an open source tool & this work can also be merged back to axios at such time as Emily (or her team) has time to pick this back up.

Not saying "go fork it," but "if you're feeling frustrated or feeling like the project is 'dead', you don't need permission to bring it back to life." The power is yours! 🌍

Probably it would be nice to have a discord for futher cooperation in the topic. Also here is not any answer on '97 opened pull requests' yet.

@emilyemorehouse @mzabriskie @nickuraltsev @rubennorte - What are your plans with axios? Last published beta version was 8 months ago, stable a year ago, you get 4,5 milion downloads a week. It's just a milion less than e.g. react. Taking into consideration this popularity it would be really cool to know what is the status and for you maybe to take some help from the community :)

@Sequoia you are quite right however it's kind of difficult at this point when there are so many open issues and PR's that it's even difficult to decide which are still valid. @emilyemorehouse wrote 2 months ago about how we can help - the first thing is to go over all the issues and do some cleaning :)

It's sad to see such a nice project slowly dying. It was literally the best http client I used in nodejs.

👍

@emilyemorehouse
I was once core team member in tldr-pages. At that time project author had some family issues and my 2nd kid was born. I understood that we will not do it ourselves and we added 3 new members to the core team to help us review PRs.

You are working in quite an important project for the internet. It should not be abandoned. There are 8 proposed PRs in the last month, none of them was merged. More importantly, there is a known security vulnerability published (https://snyk.io/vuln/SNYK-JS-AXIOS-174505), there is PR #1485 also not merged.

With that amount of PRs it would be better if you guys start accepting help. There are many people who would be proud to be the maintainer of such a project. Some of them already proposed help in this thread. Increase the number of contributors.

Good luck!

• Triage issues: I recently added issue templates to help auto-tag issues (and filter out actual bugs vs usage issues). There's _a lot_ of noise for this project and I spend the majority of my time trying to filter through issues and wind up closing most of them with a simple "This doesn't seem like an Axios bug (many I can't even duplicate),

Maybe you could adopt lodash style issue management?
(Thanks, @zachleat for promoting this in @11ty/eleventy!)

@emilyemorehouse
I see you merged 6 PRs (3 of them are for README.md). This is great start.

But honestly, I still believe you need to add collaborators to the project, because you have a lot of work.

1. As you merged security fix, you need to do an immediate release (something like v0.18.1).
2. You have 100+ PRs. Team of collaborators needs to review them and merge / decline.
3. Axios has 500+ issues. Many of them are duplicates or not relevant. Collaborators team need to regularly review them and keep the amount of open issues low, or at least managable.
4. And more importantly, your team needs to have regular routine on reviewing PRs and issues, so the situation will not repeat.

Please start accepting help, otherwise the project will become dead. Best wishes!

I think we (the community) can help relieve some workload by doing code reviews on PRs. You dont need to be a collaborator for that and reviewing is a time intensive task.

We still need people to merge PRs though.

We can also help out with basic triaging of issues by commenting things like "Duplicate of #x" and giving our opinion on feature requests.

I'm willing to chip in too but I'm not certain on what do we need to unblock the release it's cooking (which includes the DoS vulnerability fix, an important one to release).

Please, if there's any way I can help here, reach out!

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.

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

You are the owners in Axios.

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

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 :+1:

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.

I love axios, keen to help however I can

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

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

@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

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 ?

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

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.

Is there any plan to add HTTP/2 support for node.js? https://github.com/axios/axios/issues/1175

Looks like a pretty alive project to me...

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. :)

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.

What about esm version?
https://github.com/axios/axios/issues/1879

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

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?

@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.

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.

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

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