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

@termuijs/testing

v0.1.3

Published

In-memory test renderer for TermUI components with query and input simulation

Downloads

214

Readme

@termuijs/testing

Test renderer for TermUI components. Renders your JSX tree into an in-memory screen buffer, then gives you methods to query the output, simulate key presses, and check what's on screen. No real terminal needed.

The API follows the same pattern as React Testing Library: render, query, interact, assert.

Install

npm install --save-dev @termuijs/testing

Works with Vitest (recommended) or any test runner.

Quick start

import { describe, it, expect } from 'vitest'
import { render } from '@termuijs/testing'
import { useState, useInput } from '@termuijs/jsx'
import { Text } from '@termuijs/widgets'

function Counter() {
    const [count, setCount] = useState(0)
    useInput((key) => {
        if (key === '+') setCount((c) => c + 1)
    })
    return <Text>Count: {count}</Text>
}

describe('Counter', () => {
    it('starts at zero', () => {
        const t = render(<Counter />)
        expect(t.getByText('Count: 0')).toBeTruthy()
        t.unmount()
    })

    it('increments on +', () => {
        const t = render(<Counter />)
        t.fireKey('+')
        expect(t.getByText('Count: 1')).toBeTruthy()
        t.unmount()
    })
})

API

| Method | Description | |--------|-------------| | render(element, opts?) | Render into a virtual screen (default 80x24). Returns a TestInstance | | t.getByText(text) | Find first widget containing that text, or null | | t.getAllByText(text) | Find all widgets containing that text | | t.getAllByType(Type) | Find all widgets of a given constructor | | t.lastFrame() | Current screen as an array of strings (one per row) | | t.toString() | Joined non-empty screen rows | | t.fireKey(key, mods?) | Simulate a key press. Dispatches to useInput handlers | | t.typeText(text) | Type characters one by one | | t.rerender(element?) | Re-render, optionally with a new root element | | t.unmount() | Clean up all component state. Always call this |

Testing with stores

Call destroy() on your stores in afterEach to reset state between tests.

afterEach(() => {
    useCounterStore.destroy()
})

Testing with context

Wrap the component in a Provider to supply test values.

const t = render(
    <ThemeCtx.Provider value={testTheme}>
        <MyComponent />
    </ThemeCtx.Provider>
)

Snapshot testing

lastFrame() returns the rendered screen as a string array, which works with Vitest's toMatchSnapshot:

expect(t.lastFrame()).toMatchSnapshot()

Documentation

Full docs at www.termui.io/docs/testing/overview.

License

MIT