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 🙏

© 2025 – Pkg Stats / Ryan Hefner

vitest-browser-webawesome

v1.0.5

Published

Render Web Awesome components in Vitest Browser Mode

Readme

Vitest Browser Web Awesome

npm CI

Easily test Web Awesome components in Vitest's browser mode. This library ensures Web Awesome components and CSS are fully loaded before your tests run by dynamically loading only those that are referenced in the tests.

Getting Started

Prerequisites

This library is designed to work with any Vitest browser integration that provides a page.render function, including custom renderers. The primary example uses vitest-browser-preact.

See the Vitest Browser Mode documentation for a list of available integrations for common frameworks.

Installation

pnpm add -D vitest-browser-webawesome

Setup

To enable the library for all your browser tests, add it to a file in your setupFiles in your vitest.config.ts:

// In setup.ts
import "vitest-browser-preact"; // Must be imported before this library
import "vitest-browser-webawesome";

// ... other test setup, including custom CSS
// In vitest.config.ts
import { defineConfig } from "vitest/config";

export default defineConfig({
  test: {
    setupFiles: ["setup.ts"],
    // ... other browser options
  },
});

Alternatively, you can import it at the top of individual test files:

import "vitest-browser-preact";
import "vitest-browser-webawesome";

Example Test

Here is an example of testing a simple Preact component that uses a <wa-button>.

// tests/Counter.test.tsx
import { expect, test } from "vitest";
import { page } from "@vitest/browser/context";
import { useState } from "preact/hooks";

type CounterProps = {
  initialCount: number;
};

const Counter = (props: CounterProps) => {
  const [count, setCount] = useState(props.initialCount);
  return (
    <wa-button variant="brand" onClick={() => setCount(count + 1)}>
      Clicked {count} times
    </wa-button>
  );
};

test("renders and updates after click", async () => {
  // Make sure to await the render call
  await page.render(<Counter initialCount={0} />);

  // The button is ready for interaction
  const button = page.getByRole("button", { name: "Clicked 0 times" });
  await expect.element(button).toBeVisible();

  await button.click();

  // The component updates as expected
  await expect.element(page.getByText("Clicked 1 times")).toBeVisible();
  await expect
    .element(page.getByText("Clicked 1 times"))
    .toMatchScreenshot("clicked-once");
});

Supported Frameworks

This library has been tested with vitest-browser-preact. It should be compatible with any other vitest-browser-* integration that correctly implements the page.render function. You can use a custom render function so long as you use the following to add it to page:

page.extend({
  render: customRenderFunction,
});

Contributing

Feel free to open issues and pull requests. All contributions are welcome!

License

MIT