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

baldrick-zest-engine

v1.0.0

Published

DECOMMISSIONED: Prefer classic unit tests with AI assistance; see README for migration.

Downloads

101

Readme

baldrick-zest-engine

npm Build status npm bundle size npm type definitions node-current NPM

Project status: Decommissioned

This project explored a YAML-based format to author unit tests quickly. While useful in places, our current practice favors classic unit tests supported by generative AI and small helper libraries. As a result, baldrick-zest-engine is decommissioned and not recommended for new work.

Highlights:

  • Written in TypeScript (ESM).

Why decommissioned?

  • Maintenance and onboarding costs outweighed benefits of YAML indirection.
  • Modern AI-assisted workflows make writing conventional tests fast and clearer.
  • Existing ecosystem tools (Node test runner, Vitest/Jest) cover the needs better.

Recommended approach

  • Write classic tests (Node --test, Vitest, or Jest) and use generative AI to scaffold cases.
  • Compose data shaping with helpers like:
    • object-crumble for structured object mutation/abstraction
    • baldrick-zest-mess for lightweight table-driven and diff helpers

Example (Node test runner):

// test/my-feature.test.ts
import { strict as assert } from 'node:assert';

const addPrefix = (p: string, v: string) => `${p}${v}`;

test('adds prefix', () => {
  assert.equal(addPrefix('pre-', 'value'), 'pre-value');
});

// Table-driven
for (const [p, v, out] of [
  ['pre-', 'a', 'pre-a'],
  ['x-', 'b', 'x-b'],
]) {
  test(`adds prefix ${p} to ${v}`, () => {
    assert.equal(addPrefix(p, v), out);
  });
}

Status and support

  • No new features planned; security updates only (if any).
  • Consider migrating YAML specs to equivalent TypeScript tests using the example above and helpers as needed.

Documentation and links

Related

Installation (legacy)

This package is ESM-only. Installation is not recommended for new projects; retained for archival testing only.

npx baldrick-zest-engine --help

To inspect the repository locally:

git clone https://github.com/flarebyte/baldrick-zest-engine.git
cd baldrick-zest-engine
yarn