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

@decoyhq/testplane

v0.4.0

Published

Testplane plugin for the native Decoy runtime.

Readme

@decoyhq/testplane

Testplane plugin for the native decoy runtime.

npm i -D @decoyhq/cli @decoyhq/testplane
// .testplane.conf.ts
export default {
  plugins: {
    '@decoyhq/testplane': {
      url: 'http://127.0.0.1:8080',
      command: 'decoy serve',
      urls: '**/api/**', // browser requests sent to Decoy
      collection: 'happy-path', // each test's Session starts here
    },
  },
} satisfies ConfigInput

// some.testplane.ts
import { decoy } from '@decoyhq/testplane'

it('empty state', async ({ browser }) => {
  await decoy(browser).useCollection('empty')
  await decoy(browser).useRoute('users-by-id:user-123:missing') // or ('users-by-id', 'user-123', 'missing')
  await decoy(browser).reset()
})
  • The master process starts command on RUNNER_START unless Decoy already answers GET /__decoy__/health at url (reuse allowed locally, refused when CI is set), and stops it on RUNNER_END only if it started it.
  • Each test gets its own Session: a root beforeEach checks Decoy's health, applies collection, and a root afterEach ends the Session. decoy(browser) is that Session's Router.
  • With urls, matching requests from every page of the test's browser go to Decoy with x-mock-session set. Chrome rewrites the request URL itself (CDP Fetch.continueRequest), so method, headers, and body are kept and the page sees its own origin. If Decoy is unreachable the request fails; it never reaches the real network. Requests between tests are aborted.
  • Chrome/Chromium only for now (CDP through browser.getPuppeteer()), in WebDriver Classic and BiDi (webSocketUrl: true) sessions. With urls on another browser, each test fails with a clear error.