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

playwright-odiff

v4.3.8

Published

Playwright custom matcher using odiff for screenshot comparison

Readme

playwright-odiff

This is a drop-in replacement for .toHaveScreenshot() expect matcher that is a way faster than a built-in one (and when I am talking way faster I mean 8-10x on the average github actions CI machine) and it is a way more reliable.

Drop-in

Yes, it's drop in replacement. Meaning that it is going to use the same screenshots you already done with Playwright, it will put the screenshots in the same folder as Playwright does and so on and so on.

Installation

npm install playwright-odiff

Add this to the top-level setup script. The place where you configure your test, extend, or just any other common entrypoint to your Playwright tests:

import "playwright-odiff/setup"

Which is equivalent to

import { expect } from "@playwright/test";
import { toHaveScreenshotOdiff } from "playwright-odiff/toHaveScreenshotOdiff";
import "playwright-odiff/types";

expect.extend({
  toHaveScreenshotOdiff,
});

At this point you are good to go and start using it everywhere and forget about it

# if you are on macos already install GNU sed: brew install gnu-sed
sed -i -E 's/(await expect\([^)]*\))(\.not)?\.toHaveScreenshot\(/\1\2.toHaveScreenshotOdiff(/g' ./**/*.spec.ts

How does it work?

Similar to the Playwright matcher it runs a burst of screenshots that are ensuring that the content on a screen is stable but in addition to that the underlying algorithm for detecting anti-aliasing is way more stable than the pixelmatch that is used by Playwright and the threshold sensitivity is more correct (so you can safely get rid of your maxDiffPixels and maxDiffPixelsRatio even though we fully support them)