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

hereby-tools

v1.2.0

Published

Small collection of highly opinionated tools to work with Hereby task runner

Readme

hereby-tools

hereby-tools is a small, opinionated set of helpers for hereby task files. It keeps common task plumbing—running local commands, removing generated directories, and building namespaced task groups—consistent across projects.

The package is ESM-only and requires Node.js 22 or newer.

Installation

Install hereby alongside this package because it is a peer dependency:

npm install --save-dev hereby hereby-tools

taskP

taskP wraps hereby's task function and passes two project-aware helpers to the task's run callback:

  • exec(label, options?) creates an execa command runner. It prefers executables from the project's local node_modules/.bin and prefixes stdout and stderr with the task name, label, and stream name.
  • rmRf(path) recursively removes a file or directory. Relative paths are resolved from the process's current working directory.
// Herebyfile.mjs
import { taskP } from 'hereby-tools';

export const clean = taskP({
	name: 'clean',
	description: 'Remove generated files',
	run: async ({ rmRf }) => {
		await rmRf('dist');
	}
});

export const build = taskP({
	name: 'build',
	description: 'Compile the project',
	dependencies: [clean],
	run: async ({ exec }) => {
		await exec('typescript')`tsc --build`;
	}
});

export default build;

Command options supported by the text-output form of Execa can be supplied as the second argument. The helper manages stdout, stderr, and stdio itself.

await exec('tests', {
	cwd: 'packages/api',
	env: { NODE_ENV: 'test' }
})`vitest run`;

Output is formatted like this:

[build:exec:typescript:stdout] ...
[build:exec:typescript:stderr] ...

createSubmodule

createSubmodule(prefix, definitions) creates a group of taskP tasks whose names use the form <prefix>:<key>. Use moduleDependencies to refer to other tasks in the same group by key. Regular dependencies can still contain tasks defined elsewhere.

// Herebyfile.mjs
import { createSubmodule } from 'hereby-tools';

const api = createSubmodule('api', {
	clean: {
		description: 'Clean API output',
		run: async ({ rmRf }) => {
			await rmRf('packages/api/dist');
		}
	},
	build: {
		description: 'Build the API',
		moduleDependencies: ['clean'],
		run: async ({ exec }) => {
			await exec('typescript', {
				cwd: 'packages/api'
			})`tsc --build`;
		}
	},
	test: {
		description: 'Test the API',
		moduleDependencies: ['build'],
		run: async ({ exec }) => {
			await exec('vitest', {
				cwd: 'packages/api'
			})`vitest run`;
		}
	}
});

export const apiClean = api.clean;
export const apiBuild = api.build;
export const apiTest = api.test;
export default api.test;

The resulting task names are api:clean, api:build, and api:test:

npx hereby api:build
npx hereby api:test

Unknown or circular moduleDependencies are rejected while the task group is created.

Development

npm run build
npm run typecheck
npm run lint

License

MIT