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

stealthbrowser

v1.0.0

Published

Stealth-like HTTP client + jsdom page sandbox with spoofed browser APIs.

Downloads

86

Readme

stealthBrowser

Librería Node.js que combina:

  • Cliente HTTP/HTTPS con manejo de cookies, redirects, headers “tipo Chrome”, y descompresión gzip/deflate/br.
  • “Navegación” de páginas HTML usando jsdom, ejecutando scripts y exponiendo varias APIs típicas del navegador (navigator, screen, storage, permissions, etc.) con valores configurables.

Nota: esto no es un navegador real (no hay motor de render real). Está pensado para scraping/automatización ligera cuando necesitas HTML + scripts en un sandbox.

Instalación

npm i stealthBrowser

Import / Require (ESM y CommonJS)

ESM

import StealthBrowser from "stealthBrowser";

const browser = StealthBrowser.create({ debug: false });

CommonJS

const StealthBrowser = require("stealthBrowser");

const browser = StealthBrowser.create({ debug: false });

Quick start

import StealthBrowser from "stealthBrowser";

const browser = StealthBrowser.create({
  language: "es-ES,es;q=0.9,en;q=0.8",
  timezone: "America/Managua"
});

const page = await browser.navigate("https://example.com");

console.log(page.title);
console.log(page.status);
console.log(page.fingerprint.canvas);
browser.close();

API

StealthBrowser.create(options?)

Crea una instancia.

Opciones comunes (todas opcionales):

  • userAgent (string)
  • language (string)
  • timezone (string)
  • locale (string)
  • platform (string)
  • screen (obj) { width, height, depth, availWidth, availHeight }
  • hardwareConcurrency (number)
  • deviceMemory (number)
  • headers (obj) headers extra/override
  • cookies (obj) cookies iniciales { name: value }
  • proxy (obj) configuración para http(s).request (avanzado)
  • maxRedirects (number)
  • timeout (ms)
  • debug (boolean)
  • Toggles: webRTC, canvasNoise, audioContextNoise, mediaDevices, batteryAPI

browser.get(url, headers?) / browser.post(url, data, headers?)

Devuelve:

{
  status: number,
  statusText: string,
  headers: Record<string, string | string[]>,
  body: Buffer,
  rawBody: Buffer,
  url: string,
  redirected: boolean,
  type: string
}

Ejemplo:

const res = await browser.get("https://httpbin.org/headers");
// Tip: body es Buffer
console.log(res.status, res.body.toString("utf8"));

browser.navigate(url, headers?, options?)

Si la respuesta es HTML, retorna un “page context” con jsdom:

{
  pageId: string,
  url: string,
  status: number,
  headers: any,
  html: string,
  window: Window,
  document: Document,
  title: string,
  cookies: Array<Cookie>,
  fingerprint: Fingerprint,
  localStorage: Map,
  sessionStorage: Map
}

Ejemplo:

const page = await browser.navigate("https://example.com");
console.log(page.document.querySelector("h1")?.textContent);

Interacción ligera: click, type, evaluate

browser.click(selector, page)

Simula eventos de mouse y, si el elemento es <a> navega automáticamente.

const page = await browser.navigate("https://example.com");

// click en un link
const next = await browser.click("a", page);
console.log(next.url);

browser.type(selector, text, page)

Asigna el valor y dispara eventos básicos.

await browser.type('input[name="q"]', "hola", page);
// (comentario) no es un teclado real; solo dispara eventos comunes

browser.evaluate(page, script)

Ejecuta JS en un contexto con window y document.

const result = await browser.evaluate(page, "return document.title;");
console.log(result);

Cookies

  • Se guardan cookies de Set-Cookie automáticamente.
  • browser.clearCookies(domain?) borra por dominio o todas.
  • browser.getHistory() devuelve historial de requests.
  • browser.clearStorage(pageId?) limpia storage y timers.

Recomendaciones

  • Si un sitio depende mucho de APIs no soportadas por jsdom o de renderizado real, esto no va a ser suficiente.
  • Ajusta timeout y maxRedirects según el target.
  • Usa debug: true para ver errores de ejecución de scripts.

License

MIT