Replacing request in Node.js

Open
#190 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
node.js
Domain
backend

Research direction

Start with this issue and its first comments, which contain examples of how request is used. Identify the required calling conventions and compare them with the proposed Node.js HTTP options. Done means agreeing on a replacement approach and defining the supported API, but no implementation location or tests are named.

Written by the indexing model from the issue text.

Description

request is deprecated.

I want to write a new request, that has similar calling conventions, limited to the subset I use in my apps, that calls some interface to HTTP that's not being deprecated.

I understand that a lot of people are using fetch. But which one? I don't care about stylistic considerations because all the details are going to be hidden behind a simple and familiar API.

So the question is this -- how are you moving on from request?

Never mind whether this is a good idea, this is about doing the work to get beyond this deprecation with minimal pain.

In the first few comments I provide examples of how I use request in my codebase.

Thanks in advance.

Dominant language
HTML
Stars
134
Forks
10
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 scripting/Scripting-News

All issues in scripting/Scripting-News

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.