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

todomvc-tests

v1.0.0

Published

E2E Testsuite for http://todomvc.com Implementations with https://playwright.dev/

Readme

TodoMVC Tests

Playwright based E2E test suite for http://todomvc.com implementations

This is a Playwright re-implementation of todomvc-e2e-cy-testsuite, covering the same behaviour described in the TodoMVC app spec.

Usage

Install the package and the Playwright browsers, then point it at a running TodoMVC app.

npm install todomvc-tests
npx playwright install --with-deps

Run the suite headlessly against an app running on http://localhost:4200:

npx todomvc-tests headless

Run it in Playwright's interactive UI mode:

npx todomvc-tests ui

Point either command at a different port with --port / -p:

npx todomvc-tests headless --port 3000

Browsers

By default the suite runs against all three browser engines configured in playwright.config.ts (Chromium, Firefox, WebKit) - both npx todomvc-tests headless/ui and npm test exercise all three. This works the same way on Windows, macOS, and Linux: Playwright ships its own browser binaries for every platform (WebKit on Windows is Playwright's own WebKit build, not Safari), downloaded via npx playwright install (or --with-deps as shown above).

To run against a single browser, call the Playwright CLI directly with --project (the todomvc-tests CLI wrapper doesn't forward extra flags):

npx playwright test --project=chromium
npx playwright test --project=firefox
npx playwright test --project=webkit

The same flag works with UI mode (npx playwright test --ui --project=chromium), or you can just toggle projects on/off in the UI mode sidebar after launching it with npx todomvc-tests ui.

Notes on visibility

Some TodoMVC implementations hide elements (e.g. .main, .footer, .edit, .clear-completed) with CSS such as display: none, while others simply don't render them in the DOM until they're needed. Assertions in this suite use Playwright's toBeHidden() / toBeVisible(), which treat "detached from the DOM" and "present but hidden" as equivalent - so both implementation styles are handled correctly.

Development

npm install
npm test          # runs the suite headlessly (BASE_URL / PORT env vars configure the target app)
npm run test:ui    # Playwright UI mode

The target app's base URL defaults to http://localhost:4200 and can be overridden with the BASE_URL or PORT environment variables, or via the todomvc-tests CLI's --port flag.