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

@sometic/commands

v0.2.1

Published

Framework-free command registry for Sometic apps.

Readme

@sometic/commands

Framework-free command registry for Sometic: register named actions, gate them with canExecute, run them with shared context, and observe register/execute/error events.

createCommandRegistry is the bus behind toolbars, shortcuts, and command palettes. It does not render UI. A palette can search labels; this package owns identity, execution, and disposal.

Why it exists: apps accumulate one-off onClick handlers until the same action must run from a menu, a hotkey, and a test. A registry keeps one execute path so every surface stays honest about availability and errors.

Depends on @sometic/core only.

Docs: introduction and https://sometic.dev.

Install

pnpm add @sometic/commands
npm install @sometic/commands
yarn add @sometic/commands

Usage

import { createCommandRegistry } from "@sometic/commands";

const commands = createCommandRegistry();

const unregister = commands.register({
    id: "document.save",
    label: "Save document",
    canExecute: (context) => context?.["dirty"] === true,
    execute: async (context) => {
        await saveDocument(context?.["id"]);
        return "saved";
    },
});

if (commands.canExecute("document.save", { dirty: true, id: "doc-1" })) {
    await commands.execute("document.save", { dirty: true, id: "doc-1" });
}

unregister();
commands.dispose();

Listen for lifecycle events:

const stop = commands.subscribe((event) => {
    if (event.type === "error") report(event.error);
});

stop();

API

  • createCommandRegistry({ onEvent? }).
  • register(command) returns an unregister function.
  • unregister(id), has(id), list(), get(id).
  • canExecute(id, context?), execute(id, context?).
  • subscribe(listener), dispose(), disposed.

Duplicate ids, blank ids, unknown commands, blocked canExecute, and calls after dispose() throw typed errors (COMMAND_*). Execute failures rethrow after emitting an error event.

When not to use

Skip it when you have a single button with a single handler. Prefer a full workflow engine when you need durable sagas, retries, or server-driven steps. Pair with @sometic/history when actions must undo; this registry does not keep an undo stack by itself.

Docs

License

MIT