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

@electrovir/rebrowser-playwright

v1.61.101

Published

A drop-in replacement for playwright patched with rebrowser-patches. It allows to pass modern automation detection tests.

Readme

rebrowser-playwright

A fork of https://www.npmjs.com/package/rebrowser-playwright, updated to newer Playwright versions.

Versioning

The first two version segments track the upstream Playwright version this fork is based on. The patch segment is fork-local and encodes the upstream patch plus this fork's revision as <upstream-patch><fork-revision>, zero-padded so it always sorts after the upstream release.

The fork revision starts at 00, so the initial publish for a given Playwright base ends in 00: 1.61.100 is based on Playwright 1.61.1 with no fork-only changes yet. A fork-only fix that does not change the underlying Playwright version bumps the revision: 1.61.101, then 1.61.102, and so on. When the upstream base changes to 1.61.2, the fork versions restart at 1.61.200.

This package's version is kept in lockstep with @electrovir/rebrowser-playwright-core (the aliased playwright-core dependency), so a fork fix in the core bumps the revision here too.

This keeps the fork's version pinned to a recognizable upstream base while still sorting after that base (so ^1.61.x consumers pick it up) and avoiding collisions with real upstream patch releases. Do not use a pre-release tag (e.g. 1.61.1-fix.1) for fork fixes: pre-releases sort before 1.61.1 and are excluded from normal semver ranges.