Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Get rid of Axios

Open
  • Is something wrong?
#380 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, typescript
Domain
backend-api-design

Research direction

Start by locating Axios usage and the client’s request tests or entry points; the issue does not name specific files. Assess whether Fetch can cover the client’s request behavior, then define the replacement scope and verify the existing request behavior still works. Done means Axios is removed and the client works with Fetch, but the issue does not specify compatibility requirements or tests.

Written by the indexing model from the issue text.

Description

Hi,

Is it an idea to get rid of Axios and replace it with the Fetch-api?
I don't see any situation that cannot be handled using the fetch API?

Dominant language
TypeScript
Stars
572
Forks
101
Avg merge
12h 10m
Merged PRs (30d)
4

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from typesense/typesense-js

All issues in typesense/typesense-js

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.