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

@mayurajs/browser-browserless

v1.2.0

Published

Browserless browsers for mayura/browser, hosted or self-hosted.

Readme

@mayurajs/browser-browserless

Browserless browsers for mayura/browser, hosted or self-hosted: each is a fresh browser that Browserless launches when its CDP connection opens and ends when it closes. From any runtime, with no dependency.

npm install mayura @mayurajs/browser-browserless
import { createBrowsers } from 'mayura/browser';
import { browserlessBrowsers } from '@mayurajs/browser-browserless';

const browsers = createBrowsers(browserlessBrowsers({ token }), {
  maxBrowsers: 2, maxLifetimeMs: 15 * 60_000,
  origins: ['https://example.com'],
});
const browser = await browsers.open();
await browser.goto('https://example.com/');
await browser.release();
  • Each browser is one connection to Browserless: nothing is kept between browsers (this is not Browserless's persistent Session API). Releasing the browser closes the connection, which ends it; Browserless ends it at its lifetime, given as the connection's timeout, should that never happen. Browserless's plans cap a browser at 2 minutes to an hour.
  • Since every connection is a browser of its own, a browser gives no cdp endpoint to other clients: Stagehand and @mayurajs/browser-agent-browser cannot join it.
  • Hosted regions are production-sfo (the default), production-lon and production-ams. For your own Browserless, give endpoint, such as wss://browserless.internal; plain ws:// only on this machine.
  • Ad blocking and stealth are off unless asked for; no proxy is used. There is no live view.
  • The token travels in the connection's query, as Browserless takes it: treat the URL as a secret; Mayura never logs it.
  • Origins are enforced inside the browser, by intercepting its requests over CDP; a live check against Browserless confirmed it on October 6, 2026. Should a connection ever not allow that, opening a browser fails rather than running unchecked.
  • Options: token, region, endpoint, blockAds, stealth, maxLifetimeMs (1 hour).

See the browser guide. Apache-2.0.