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

@tayomi/utils

v0.2.0

Published

Process-edge Node primitives shared across the TAYOMI plugins and modules: every entry exists to retire a cross-boundary clone, never to collect helpers.

Downloads

356

Readme

@tayomi/utils

Process-edge Node primitives, consumed by the TAYOMI framework and by @tayomi/cc-views as a regular npm dependency. Built inside the tayomi workspace for now; the target shape is an autonomous package in its own repository (the workspace is the construction site, not the owner).

Charter (what earns an entry here)

Every function in this package exists to retire a cross-boundary clone: the same code was maintained in two or more packages that may not import each other (layering rule no-sibling-plugin-import), and drifted-copy risk is the whole reason this package exists. Concretely:

  • Tiny, dependency-free, Node-only. A primitive an entrypoint needs at the process edge. Anything with a domain (TAYOMI's wire formats, specs, gate vocabulary) does NOT belong here.
  • No module-level state, no side effect at import (sideEffects: false is a promise, not an optimization flag).
  • No main(), ever. A module carrying a self-exec guard must never be imported (one-main-per-process, commit 249da20).
  • Each function carries the why of its existence: the incident or the clone it retired.

Not a junk drawer: a helper that only one package uses lives in that package.

Import contract

Two doors, both stable; the file layout underneath is neither:

import { isDirectExecution } from '@tayomi/utils';          // the root barrel
import { readStdinSync } from '@tayomi/utils/io';           // a domain subpath

A domain is born with its first function, never empty. Current domains:

| Domain | Contents | | --- | --- | | process | isDirectExecution (the entrypoint guard: real paths on both sides) | | io | readStdin, readStdinSync, parseStdin (the stdin kit: TTY guard, joined-buffer decode, EAGAIN-as-not-yet); stringField (the payload interrogation every hook edge retypes) | | ansi | sgr, RESET, BOLD, DIM (one-line notice styling; anything richer is @tayomi/cc-views) |