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

@native-dom/vitest

v0.0.10

Published

Vitest environment backed by native-dom.

Downloads

114

Readme

@native-dom/vitest

Vitest environment for native-dom.

This package creates a Window from @native-dom/runtime, copies compatible host globals such as fetch, Blob, URL, and typed arrays into the window when needed, then uses Vitest's populateGlobal() helper to install browser globals for each test environment.

Usage

// vitest.config.ts
import { defineConfig } from "vitest/config";

export default defineConfig({
  test: {
    environment: "native-dom"
  }
});

Install vitest-environment-native-dom for the config above. Vitest resolves custom environments by package name, so environment: "native-dom" loads vitest-environment-native-dom, which re-exports this package.

For CLI experiments you can also point Vitest at the built environment file:

pnpm exec vitest run --environment ./node_modules/@native-dom/vitest/dist/index.js

Profiling

Set NATIVE_DOM_VITEST_PROFILE=1 to emit setup and teardown timing records to stderr:

NATIVE_DOM_VITEST_PROFILE=1 pnpm exec vitest run

The benchmark harness parses these records to track environment overhead in real-world suites.

Compatibility Switches

Set NATIVE_DOM_VITEST_DISABLE_MATCH_MEDIA=1 when a suite installs its own matchMedia mock only if the API is missing. This keeps those suites on their existing mock path while still using native-dom for the rest of the environment.

Legacy Entry

src/legacy.ts exports the same environment with transformMode: "web" for older Vitest suites that still depend on the legacy environment shape.

Development

pnpm --filter @native-dom/vitest build
pnpm --filter @native-dom/vitest typecheck
pnpm --filter @native-dom/vitest test