RetroSearch Browse

Showing content from https://github.com/bitinn/node-fetch/issues/567 below:

(Sometimes you gotta write a clickbait issue to get people's attention.)

The current status of node-fetch is fine:

I believe 95% of the Fetch API use cases are covered either by us or other implementations.
node-fetch is lean enough (150KB, zero dependency), people can write their own wrapper or even fork our code to fit their own purpose.
Fetch API is now quite stable so we are not dealing with many breaking changes.
In short, if you are on 1.x or 2.x releases, and it works for you, great, no need to worry.

The future status of node-fetch could be better:

It doesn't have an active maintainer, (contributors) all have their own lives.
There are certainly things we would like to work on to make node-fetch easier to use. (see open PRs).

What to do?

We need an active maintainer: someone need to own this package's npm publishing right, and have free time and proper motivation to maintain node-fetch changelog and releases.
We need a small team that help on non-trivial things: like making a PR spec compliant, which again require free time and proper motivation.

If you are such a candidate, or better yet, can negotiate with your employer to be payed to maintain node-fetch, let us know in the comments.

buu700, busticated, anothertempore, amio, styfle and 28 moreparamsiddharth, lonevetad and YDX-2147483647

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4