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

tsds-web-test-runner

v1.21.0

Published

Development stack for TypeScript libraries

Readme

tsds-web-test-runner

This package is an internal command adapter for running browser tests through ts-dev-stack, not a standalone end-user command.

Install the parent CLI and this adapter locally so browser installation uses the adapter's resolved Playwright version.

The default configuration runs Chromium, Firefox and WebKit. Their matching Playwright binaries and OS dependencies must be installed before running tests. The browser installation step below uses the locally installed Playwright CLI. Provide browser tests using Mocha's describe and it under test/**/*.test.{ts,tsx,jsx,mjs} before running the test command.

npm install --save-dev ts-dev-stack tsds-web-test-runner
npm exec --no -- playwright install --with-deps
npm exec --no -- tsds test:browser

Repeat browser installation after changing the resolved Playwright version. If you set PLAYWRIGHT_BROWSERS_PATH, use the same absolute path for installation and execution. See Playwright browser management and repository test setup.

Pass the Web Test Runner arguments after test:browser, for example npm exec --no -- tsds test:browser --config wtr.config.mjs.

Without an explicit test path, it runs test/**/*.test.{ts,tsx,jsx,mjs}. Add --dry-run to check command selection without opening a browser.

Starting with the planned 1.21.0 release, the adapter attempts to restore its temporary installation link after setup or test failure. A sole operation or restoration failure is reported directly. If both fail, the callback receives an Error whose errors array contains the operation error first and the restoration error second.