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

@owlmeans/test

v0.1.11

Published

Foundation helpers shared by the OwlMeans test packages and individual package test suites.

Readme

@owlmeans/test

Foundation helpers shared by the OwlMeans test packages and individual package test suites.

  • loadEnv(opts?) — locate <monorepo-root>/.env, parse it, merge into process.env (idempotent; no-op when Bun already loaded the file via --env-file).
  • requireEnv(keys) — returns { ok: true } or { skip: true, reason } so callers can test.skip(...) when an integration variable is missing.
  • hasEnv(key) — boolean shorthand for conditional service provisioning in tests/context.ts.
  • makeGates(spec) — builds a frozen record of { <name>: { skip, reason } } so a per-package tests/context.ts exposes one source of truth and individual specs can self-skip.
  • loadFixture<T>(relPath) — JSON fixture loader rooted at the consuming package's tests/fixtures/.

Tests must be located at packages/<pkg>/tests/, named *.spec.ts. See the testing-overview skill for the full strategy.

Agent guidance

This package ships embedded Claude Code skills and GitHub Copilot instructions under agent-meta/. After installing your @owlmeans/* packages, run the OwlMeans agent-skills installer to place them into your project's native locations (.claude/skills/ and .github/instructions/):

npx @owlmeans/agent-skills

The embedded files are version-matched to this package release. Do not edit them directly — they are regenerated on each publish. To contribute guidance edits, open a PR against the source monorepo.