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

@nazehs/agent-runtime

v0.1.2

Published

Framework-agnostic agent execution engine for Node (NestJS, Next.js API routes, workers).

Readme

@nazehs/agent-runtime

Local agent execution: register handlers, call execute / executeStream, get AgentResult. Optional guardrails, tracing, and timeouts are built in.

Installation

npm install @nazehs/agent-runtime
yarn add @nazehs/agent-runtime

Usage

import { createAgentRuntime, InMemoryAgentRegistry } from '@nazehs/agent-runtime';
import type { AgentContext, AgentResult } from '@nazehs/agent-runtime';

const registry = new InMemoryAgentRegistry();
registry.register({
  name: 'my-agent',
  version: '1.0.0',
  executionMode: 'local',
  handler: myAgent,
  timeoutMs: 45_000,
});

const runtime = createAgentRuntime({
  registry,
  transportAdapters: [],
  defaultTimeoutMs: 45_000,
});

const context: AgentContext = { requestId: crypto.randomUUID() };
const result: AgentResult = await runtime.execute('my-agent', input, context);

Public types and functions are re-exported from the package entry; see the TypeScript definitions in dist/ or source index.ts.

Requirements

  • Node >= 20.10
  • ESM only ("type": "module" in your app, or dynamic import() from CommonJS)

RAG

RAG (retrieval-augmented generation) is not built into the runtime; you do it in your handler—retrieve documents or snippets, add them to the system or user message list (or a dedicated RAG field your LLM client understands), then call the model. The example support path does this by grounding the system message from a local knowledge base (example/lib/support/support-llm-prep.ts).

Tool calling

Types — AgentToolDefinition, AgentToolCall, AgentToolResult, AgentInputWithMessagesAndTools. Context — optional context.tools to list tools for the run. Traces — emitAgentToolRequested / emitAgentToolCompleted / emitAgentToolFailed, and withAgentToolCallTraced for a single call. The LLM and tool↔message loop are implemented in your code; see example/lib/support for a Chat Completions tools / tool_calls loop and lookup_rentamnow_knowledge.

More

Full app example, env, git/tarball installs, and release process for this package live in the monorepo: github.com/Nazehs/agent-engine (see the root README and example/).

License

MIT — see LICENSE.