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

@open-panel/action-engine

v0.1.0

Published

Action registry and execution engine for OpenPanel, plus the built-in actions: shell, hotkeys, open app/URL, page navigation, folders, multimedia keys and profile switching.

Readme

@open-panel/action-engine

Resolves and executes actions end-to-end for OpenPanel: button press → resolve action → validate config → execute → success/failure, always with an execution id, plus the built-in action catalog (shell, hotkeys, open app/URL, page navigation, folders, multimedia keys, profile switching).

Requires Node — built-in actions shell out via node:child_process.

Install

npm install @open-panel/action-engine

What's in here

  • ActionRegistry — holds every known action type (built-in and plugin-provided alike) keyed by type. register/unregister/resolve/list.
  • ActionEngine — runs ActionRegistry.resolve → configSchema.parse → definition.execute(ctx, config), with a per-execution timeout (default 30s) and onStarted/onFinished/onFailed listeners. An action or plugin throwing is always caught and turned into a failed execution — it never crashes the host.
  • ActionDefinition<TConfig> — the shape of one action: type, name, optional configSchema (a zod schema), and execute(ctx, config).
  • ActionContext — the only surface an action's execute() touches: log, shell, and (when the host wires them up) navigateToPage, navigateRelativePage, switchProfile, enterFolder, exitFolder, toggleSwitch.
  • builtInActions — the MVP action catalog: openAction, openUrlAction, openAppAction, hotkeyAction, hotkeySwitchAction, shellAction, typeTextAction, multimediaAction, changePageAction, nextPageAction/previousPageAction, switchProfileAction, openFolderAction/backFolderAction, pageIndicatorAction.
  • runShellCommand — the node:child_process wrapper the shell-based built-ins use, exposed for plugins that need the same behavior.

Usage

import { ActionEngine, ActionRegistry, builtInActions } from "@open-panel/action-engine";

const registry = new ActionRegistry();
for (const action of builtInActions) registry.register(action);

const engine = new ActionEngine(registry, {
  navigateToPage: async (pageId) => { /* switch the active page */ },
});

engine.onFailed((error) => console.error("action failed", error));

await engine.execute({ type: "url.open", config: { url: "https://example.com" } });

Defining a custom action:

import { z } from "zod";
import type { ActionDefinition } from "@open-panel/action-engine";

const configSchema = z.object({ message: z.string() });

const notifyAction: ActionDefinition<z.infer<typeof configSchema>> = {
  type: "custom.notify",
  name: "Notify",
  configSchema,
  async execute(ctx, config) {
    ctx.log("info", "notifying", { message: config.message });
  },
};

Related packages

License

MIT © OpenPanel contributors