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

@wdio/image-comparison-core

v2.1.0

Published

Image comparison core module for @wdio/visual-service - WebdriverIO visual testing framework

Readme

WebdriverIO Image Comparison Core

Installation

The easiest way is to keep @wdio/image-comparison-core as a dev-dependency in your package.json, via:

npm install @wdio/image-comparison-core --save-dev

Instructions on how to get started can be found in the visual testing docs on the WebdriverIO project page.

ignore* comparison options (pixelmatch)

v10 uses pixelmatch instead of resemble.js. The public ignore* API is preserved and mapped to resemble-style presets via last-wins semantics.

Defaults vs resemble v9

| | v9 (resemble.js) | v10 default | |---|---|---| | AA forgiveness | opt-in (ignoreAntialiasing: true) | on by default (ignoreAntialiasing: true) | | Strict comparison | default | set ignoreAntialiasing: false | | Engine | resemble RGB/brightness | pixelmatch YIQ perceptual distance |

No config change is needed if you rely on forgiving comparison behaviour.

Preset mapping

| Option | Preprocessing | pixelmatch threshold | AA forgiven | |---|---|---|---| | (none, ignoreAntialiasing: false) | - | ~16/255 (0.063) | no | | ignoreAntialiasing | - | ~32/255 (0.13) | yes | | ignoreLess | - | ~16/255 (0.063) | no | | ignoreAlpha | alpha → opaque | ~16/255 (0.063) | no | | ignoreColors | resemble luma grayscale | ~16/255 (0.063) | no | | ignoreNothing | - | 0 | no |

Thresholds are calibrated to resemble outcomes; the underlying algorithm is YIQ perceptual distance, not resemble's RGB math.

Last-wins semantics

When multiple ignore* flags are enabled, the active preset is the last one in this order (matching resemble.js):

alphaantialiasingcolorslessnothing

Example: ignoreLess: true with the default ignoreAntialiasing: true resolves to the ignoreLess preset (strict AA, not forgiving).

Golden fixture tests documenting expected pass/fail behaviour live in tests/fixtures/ignore-options/.

Comparison uses pixelmatch.