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

any-browser

v1.0.9

Published

Test your website across Safari (WebKit), Firefox, and Chrome with one CLI command.

Readme

any-browser

Test your website on Safari, Firefox, and Chrome — from any OS — with one command.

any-browser test safari
any-browser test chrome firefox
any-browser test all

Table of Contents

Getting Started

Install it globally from npm:

npm install -g any-browser

The first install downloads the Chrome, Firefox, and Safari (WebKit) engines via Playwright — that's a one-time ~300MB download, and you'll see exactly what's happening and why in your terminal. After that, every run is instant.

Usage

any-browser test <browser...> [options]

| Browser argument | Engine used | |---|---| | chrome | Chromium | | firefox | Firefox | | safari | WebKit | | all | all three |

Options:

  • -u, --url <url> — URL to test (default: http://localhost:3000)
  • --headless — run without opening a visible window

Examples:

any-browser test safari
any-browser test chrome firefox
any-browser test all --url https://example.com

🎇 Each browser opens in front of you, paused, so you can click around and inspect the page exactly like a real visitor would.

What Are The Major Browsers?

Ensuring your website looks great across all major browsers is crucial for a consistent user experience. any-browser covers Chrome, Firefox, and Safari regardless of your operating system — Linux, macOS, or Windows.

If we look at browser market share worldwide, Chrome dominates at around 64%, Safari follows with about 20%, and Firefox holds roughly 4%. While there are many other browsers, these three are critical because they use distinct rendering engines:

  • Chrome (and Chromium-based browsers like Edge and Brave) use Blink.
  • Firefox uses Gecko, developed by Mozilla.
  • Safari uses WebKit, developed by Apple.

Since Safari is exclusive to macOS, testing it from Linux or Windows normally requires workarounds. any-browser sidesteps that entirely by using Playwright's open-source WebKit build, so any-browser test safari works identically on any OS.

Running From Source Instead

Prefer to clone and run it locally rather than install globally? That still works exactly like before:

git clone https://github.com/BhalliBhai/any-browser-cli.git
cd any-browser-cli
npm install
npm run test:safari   # or test:chrome / test:firefox

Troubleshooting

If you hit missing dependencies on Linux when running WebKit tests:

npx playwright install-deps webkit

If you see an error about missing libraries such as:

browserType.launch:
Host system is missing dependencies to run browsers.
Missing libraries:
  libpcre.so.3
  libicui18n.so.66
  libicuuc.so.66
  libwebp.so.6
  libenchant.so.1
  libffi.so.

Install the necessary system packages. On Ubuntu/Debian:

sudo apt-get install -y libpcre3 libicu66 libwebp6 libenchant1c2a libffi7

For other distributions, check your package manager's docs, or just run npx playwright install-deps and let Playwright figure it out.


If this helped, consider starring ⭐ the repository to support the project! 😊


Built by Bhalli B. — Full-Stack Developer & SaaS MVP Architect.