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

@nan0web/protocol

v2.0.0

Published

Minimalistic protocol for executing commands in a message‑driven environment of NaN•Web

Readme

@nan0web/protocol

Minimalistic protocol for executing commands in a message‑driven environment. It validates input, runs a command (class or function) and returns a structured output.

Installation

How to install with npm?

npm install @nan0web/protocol

How to install with pnpm?

pnpm add @nan0web/protocol

How to install with yarn?

yarn add @nan0web/protocol

Basic usage – CommandProtocol

The protocol accepts an ExecutableCommand subclass or a plain function. It records a history of processed messages. @todo re-understand the logic of protocol commands due to new Message, UiMessage.

it.skip("How to create a CommandProtocol with a class command?", async () => { class EchoCommand extends ExecutableCommand { name = "Echo" async run(msg) { return msg.argv.join(" ") } } const protocol = new CommandProtocol({ command: new EchoCommand(), db: fs, logger: new NoConsole(), }) const input = { value: "Echo hello world", time: Date.now() } console.info(protocol.accepts(input)) // ← true const out = await protocol.process(input) console.info(out) // { content: ["hello world"], error: null, meta: { source: "Echo" }, priority: 0 } console.info(protocol.history[0].message) // Message { body: "Echo hello world", head: {} } @todo re-understand the logic of protocol commands due to new Message, UiMessage.

it.skip("How to use a plain function as command?", async () => { const fn = (msg) => msg.argv.map(v => v.toUpperCase()) const protocol = new CommandProtocol({ command: fn, db: fs, logger: new NoConsole(), }) const input = { value: "fn hello planet", time: Date.now() } const out = await protocol.process(input) console.info(protocol.accepts(input)) // ← true console.info(out.content) // ← ["HELLO", "PLANET"] console.info(out.meta.source) // ← "fn"

Object‑style command

Returning an object allows custom content, priority and meta. @todo re-understand the logic of protocol commands due to new Message, UiMessage.

it.skip("How to return an object from a command?", async () => { function ObjCmd(msg) { return { content: ["custom", ...msg.argv], priority: 7, meta: { extra: true }, } } const protocol = new CommandProtocol({ command: ObjCmd, db: fs, logger: new NoConsole(), }) const input = { value: "ObjCmd a b", time: Date.now() } const out = await protocol.process(input) console.info(out.content) // ← ["custom", "a", "b"] console.info(out.priority) // ← 7 console.info(out.meta) // ← { extra: true, source: "ObjCmd" }

Fallback response

When the command does not return a recognised shape.

How does fallback look like?

const fn = () => 12345
const protocol = new CommandProtocol({
	command: fn,
	db: fs,
	logger: new NoConsole(),
})
const input = { value: "fn any", time: Date.now() }
const out = await protocol.process(input)
console.info(out.content)
// [ "Command executed.", "(no output data)" ]
console.info(out.meta.source) // ← fn

Error handling

Thrown errors are caught and marked as critical (priority: 100).

How are errors reported?

const boom = () => {
	throw new Error("boom")
}
const protocol = new CommandProtocol({
	command: boom,
	db: fs,
	logger: new NoConsole(),
})
const input = { value: "boom test", time: Date.now() }
const out = await protocol.process(input)
console.info(out.content) // ← ["boom"]
console.info(out.priority) // ← 100
console.info(out.error instanceof Error) // ← true
console.info(out.meta.source) // ← boom

API surface

Exported symbols must be present.

All exported classes should be available

TypeScript declarations

Package provides .d.ts files

CLI Playground

Example command to run the playground script.

How to run playground script?

npm run play

Contributing

How to contribute? - check here

License

How to license ISC? - check here