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

vitest-environment-wasm-quickjs-dom

v1.0.17

Published

The wasm-quickjs-dom environment for Vitest, under the name Vitest looks for: environment: "wasm-quickjs-dom"

Readme

vitest-environment-wasm-quickjs-dom

The wasm-quickjs-dom environment for Vitest, under the name Vitest looks for.

Vitest turns environment: "<name>" into the package vitest-environment-<name> and resolves it from the project's root. This package is that name, so the config is one line, whatever the package manager does with node_modules (pnpm does not hoist, which is what breaks a path or a subpath of another package in a monorepo).

pnpm add -D vitest vitest-environment-wasm-quickjs-dom
// vitest.config.ts
import { defineConfig } from "vitest/config";

export default defineConfig({
  test: {
    environment: "wasm-quickjs-dom",
    environmentOptions: {
      wasmQuickjsDom: { url: "http://localhost:3000" }, // any JSDOMOptions
    },
  },
});

In a monorepo whose root config lists the projects of the packages, give each project its own root, so the environment is looked up from the package that depends on it:

projects: [
  {
    root: "apps/app",
    test: { environment: "wasm-quickjs-dom", include: ["test/client/**/*.test.tsx"] },
  },
],

The environment itself is wasm-quickjs-dom/vitest; its options and what it provides are described in the wasm-quickjs-dom README. This package has the same version as wasm-quickjs-dom and depends on exactly that version.