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

@canonical/svelte-ssr-test

v0.10.0-experimental.5

Published

Test package for Svelte SSR testing

Downloads

108

Readme

@canonical/svelte-ssr-test

Utilities for testing Svelte 5 server-side rendering (SSR) components with familiar @testing-library/dom queries.

It renders a Svelte component via svelte/server, mounts the HTML into a jsdom document, and returns a query API (getByText, getByRole, etc.) plus access to head, body, and html.

Installation

bun add -D @canonical/svelte-ssr-test

Usage

import { describe, it, expect } from "vitest";
import { render } from "@canonical/svelte-ssr-test";
import Greeting from "./Greeting.svelte";

describe("Greeting.svelte (SSR)", () => {
  it("renders greeting text", () => {
    const { getByText, window, container } = render(Greeting, {
      props: { name: "World" },
    });

    expect(getByText("Hello World")).toBeInstanceOf(window.HTMLElement);
  });
});

Returned API

  • queries – All @testing-library/dom queries bound to the rendered container
  • window, document – jsdom window and document
  • container – the rendered Svelte component DOM element
  • pretty(maxLength?) – pretty-prints the container HTML

Vitest Setup

Recommended options in vitest.config.ts or vite.config.ts for tests:

import { defineConfig } from "vitest/config";

export default defineConfig({
  test: {
    environment: "node", // keep pure SSR (avoid jsdom or happy-dom)
  },
});

This keeps tests running in a Node environment, while @canonical/svelte-ssr-test creates its own jsdom instance for DOM queries.

Why?

  • Familiar API: Reuse the familiar @testing-library query API for assertions, making it easy to write and maintain tests:
    const { getByText } = render(MyComponent);
    expect(getByText("Hello")).toBeInTheDocument();
  • Comprehensive Output: Access both raw SSR HTML (head, body) and a DOM representation (container), allowing you to test both the HTML output and DOM behavior:
    const { head, body, container } = render(MyComponent);
  • Testing Environment: By using node testing environment we make sure svelte SSR rendering is in it's expected server environment compared to having access to browser API with jsdom.