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

@burojs/test-helpers

v0.3.0

Published

Buro: typed Playwright Page Objects over the testid convention

Readme

@burojs/test-helpers

Typed Playwright page objects for buro apps, built over the framework's stable data-testid convention.

Because buro generates its own test ids (list-row:<resource>:<id>, picker-quickcreate:<resource>, …), your e2e tests can address a screen you never hand-wrote.

Install

pnpm add -D @burojs/test-helpers @playwright/test

Usage

import { test, expect } from '@playwright/test';
import { createBuroPage } from '@burojs/test-helpers';

test('a document can be filtered and opened', async ({ page }) => {
  const app = createBuroPage(page);
  const documents = app.resource('document_document');

  const list = documents.list();
  await list.goto();
  await list.search().fill('invoice');
  await list.paginationNext().click();

  await expect(documents.show('42').field('title').input()).toBeVisible();
});

Every locator above is derived from the resource name, so none of these test ids are hand-written in your app.

Main exports

  • createBuroPage / BuroPage — the entry point; wraps a Playwright Page. Exposes resource(name), contextPicker(slice), notification(type), actionConfirm(resource, scope, action) and the raw page.
  • createResourceObject / ResourceObject — one resource's four surfaces: list(), create(), edit(id), show(id), plus picker().
  • createFormView / FormView / FormFieldObject — form fields across create/edit/show: field(name).input(), .error(), .help(), and section(key).
  • createShowView / ShowView — the detail surface (a FormView in show mode).
  • createPickerObject / PickerObject — relation pickers, including quick-create.
  • createConfirmDialog / ConfirmDialogObject — confirmation dialogs raised by declared actions.

The list surface (documents.list()) covers goto(), row(id), search(), paginationPrev() / paginationNext(), and the filter builder: filterButton(), filterPanel(), filterAddRow(groupPath?), filterRowField(path) / filterRowOp(path) / filterRowValue(path), filterApply(), filterReset(), filterBadge(index) / filterBadgeRemove(index), filterClearAll() and filterPinned(field).

License

MIT