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

@echo-agent/base

v0.2.0

Published

Echo's assembly layer: the launcher parts, the product contract, the shell port, host capabilities and the pipe form. No terminal dependency — a web or desktop product depends on this and brings its own shell. Requires Bun.

Readme

@echo-agent/base

Echo 的装配层。把一个产品跑起来这件事本身:参数解析、凭据、引导设置的时机、会话解析、装配、收摊、管道形态、观测面板。

它不是产品,也不是壳。依赖方向是 @echo-agent/core ← @echo-agent/base ← 壳与各产品。

这里没有任何界面技术。 交互形态由产品在自己的入口挑一个 Shell 实现交进来:

import { mainFor, conductEntry, type Product } from "@echo-agent/base";
import { terminalShell } from "@echo-agent/tui"; // 或者你自己的 web / 桌面实现

const MY_PRODUCT: Product = {
  name: "my-agent",
  version: "0.1.0",
  preset: (form) => ({ extensions: [myIdentity(), conductEntry(form)] }),
};

export const main = mainFor(MY_PRODUCT, terminalShell);

所以做 web 界面的产品依赖本包,不必装一个终端库。

自己实现壳,就实现 Shell 这个端口的两件事:open()(界面本体)与 firstRun()(缺凭据时的引导设置)。

想完全不要这一层、把 agent 嵌进自己的程序里,用 @echo-agent/core 的 createEcho()。

许可证 MIT。需要 Bun。