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

@pwtap/platform

v1.2.0

Published

macOS-first platform seam (paths, shell, device discovery/boot, device lock) for Playwright Test Automation Platform plugins

Readme

@pwtap/platform

Platform seam for Playwright Test Automation Platform plugins — one place for OS paths, shell, device discovery/boot, and a cross-process device lock. macOS drives Android and iOS; Linux drives Android.

npm

You normally don't install this directly. It arrives as a runtime dependency of the plugins that need device/OS access (e.g. the mobile engines). Start a project with npm init @pwtap@latest.

Why

Every OS-specific command (Android SDK paths, adb, simctl, emulator boot, device locking) lives behind one interface, so engines stay OS-agnostic and new platforms are additive rather than scattered if (process.platform) branches.

import { getPlatform } from '@pwtap/platform';

const platform = getPlatform(); // MacPlatform or LinuxPlatform; throws elsewhere, naming the file to add
platform.os; // 'macos' | 'linux'

Surface

  • getPlatform()Platform (paths + shell helpers).
  • Device discovery + boot for Android AVDs and iOS simulators.
  • deviceLock — an OS-agnostic cross-process lock so two runs never boot or claim the same device.

macOS and Linux are implemented; other OSes throw a clear "add this file" error rather than silently misbehaving. A Linux host answers iOS calls with a failed RunResult instead of throwing, so device discovery and the device/app pickers report "no simulators" and stay usable — that is what runs the Android emulator on a CI runner with KVM, where a macOS runner has no hypervisor to give it.

License

MIT