npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@neykoor/node-fetch

v1.0.0

Published

Fork minimalista de node-fetch en TypeScript, con solo la superficie usada por Eris-MD

Readme

@neykoor/node-fetch

Fork minimalista de node-fetch, reescrito en TypeScript usando solo módulos nativos de Node (http, https, zlib), sin dependencias externas.

Cubre exactamente lo que usa los bots dm:

  • fetch(url, init) con GET y POST
  • body como string, Buffer, URLSearchParams, stream (form-data)
  • Seguimiento de redirects (301/302/303/307/308)
  • Descompresión automática gzip / deflate / br
  • response.ok, .status, .statusText, .headers, .url
  • response.text(), .json(), .arrayBuffer(), .buffer(), .blob()
  • response.assertContentType(mime) — lanza FetchError si el content-type no coincide (útil para detectar cuando ezgif devuelve HTML de error en vez del archivo)
  • response.headers como clase FetchHeaders (.get(), .has(), .forEach(), iterable)
  • Timeout por defecto de 30s (configurable con timeout, 0 lo desactiva)
  • Límite de tamaño de respuesta (maxContentLength, default 50MB) — corta la descarga si el header content-length o los bytes recibidos lo superan
  • Cancelación externa vía AbortSignal (signal)
  • Reintentos con backoff exponencial (retries, retryDelay) — solo ante errores de red/timeout, nunca ante 4xx/5xx

Build

npm install
npm run build

Genera dist/index.js y dist/index.d.ts.

Uso

import fetch from '@neykoor/node-fetch';

const res = await fetch('https://ejemplo.com');
if (!res.ok) throw new Error(`HTTP ${res.status}`);
const buf = Buffer.from(await res.arrayBuffer());

Instalación en el bot

En package.json del bot:

"@neykoor/node-fetch": "file:../neykoor-node-fetch"

o publicando el paquete y referenciando la versión publicada. Luego reemplazar:

import fetch from 'node-fetch';

por:

import fetch from '@neykoor/node-fetch';

en sticker.js, socket-setbanner.js, utils-toimg.js, downloads-pinterest.js y downloads-ytsearch.js.