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

@siteimprove/alfa-dom

v0.114.3

Published

Implementations of the core DOM and CSSOM node types

Readme

Alfa DOM

Implementation of the DOM and CSSOM specifications.

Test specificities

Because this is the package that defines Alfa's custom JSX transformation, the tests that use JSX syntax need to do some magic.

From other packages, setting jsxImportSource: "@siteimprove/alfa-dom" in the compilerOptions of the tsconfig.json file is enough to make the tests work.

However, this points to the compiled version of the JSX transformation (in the dist directory). This means that the resulting Element, … will be from the classes defined there. Which, in turns, means that if we point the test files to the uncomplied src directory, Vitest will make its own compilation resulting in different Element, … classes and breaking every instanceof, … checks (used, notably, in the isElement, … guards).

It seems that it is not possible to point the jsxImportSource to the src directory, which makes sense as Vitest needs a compiled version of it to run during its own compilation process.

Hence, the only way to use the same class for both the tests and the JSX transformation is to also have the tests import from dist, instead of doing it from src as usual; which also means importing from the .js compiled files instead of the .ts source files.