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

@llm4ts/runner

v0.10.1

Published

Node runner, CLI, terminal, and MCP composition for llm4ts

Readme

@llm4ts/runner

Node runner for llm4ts: the runNode embedded entry point, connector presets, terminal rendering, the llm4ts CLI, and the MCP stdio server.

Install

npm install @llm4ts/runner @llm4ts/flow @llm4ts/core effect

Requires Node.js >= 22. effect is a peer dependency pinned to the Effect 4 beta line.

Run a flow

runNode provides every Node boundary (HTTP client, process executor, temporary files, file store, connector registry) with sensible defaults — you never assemble Effect layers yourself:

import { runNode } from "@llm4ts/runner/FlowRunner"
import { ApiConnectorConfig } from "@llm4ts/core/ConnectorConfig"
import { ConnectorIds } from "@llm4ts/core/Models"
import { collect } from "@llm4ts/core/Streaming"

const program = runNode(
  {
    workDir: process.cwd(),
    workspace: process.cwd(),
    userPrompt: "Draft a small implementation plan",
    coder: ApiConnectorConfig.make({ connectorId: ConnectorIds.Mock })
  },
  (context) => collect(context.coder.executeStream(context.userPrompt))
)

The mock connector needs no credentials. Swap in a real provider via ApiConnectorConfig (API keys are read from standard environment variables such as ANTHROPIC_API_KEY) or a CLI coding agent via coderFromEnv (LLM4TS_CODER=claude|codex|gemini|...).

CLI

The package ships a llm4ts binary that streams one prompt to your configured coder and records a trace under .llm4ts/:

npx llm4ts "explain this repository" --repo .

Documentation

License

MIT