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

dev-server-log

v0.1.1

Published

AI-shareable dev server logging CLI

Readme

dev-server-log

AI-shareable dev server logging CLI.

dev-server-log wraps a dev server command and writes the same output to:

  • the terminal
  • a stable plain text log file
  • a stable JSONL log file for agents and scripts

This makes tail -F and jq useful while the command is still running.

Install

pnpm add -D dev-server-log

Usage

Wrap any command after --.

devlog --name start-dev --log .log/start-dev.log -- pnpm start:dev
devlog --name storybook --log .log/storybook.log -- storybook dev --port 6006 --no-open

--jsonl is optional. When omitted, it is derived from the plain log path.

.log/start-dev.log   -> .log/start-dev.jsonl
.log/storybook.log   -> .log/storybook.jsonl

package.json examples

{
  "scripts": {
    "dev": "devlog --name dev --log .log/dev.log -- vite dev",
    "storybook": "devlog --name storybook --log .log/storybook.log -- storybook dev --port 6006 --no-open"
  }
}

For a NestJS app:

{
  "scripts": {
    "start:dev": "devlog --name start-dev --log .log/start-dev.log -- nest start --watch"
  }
}

Reading logs

Humans can follow the plain text log:

tail -F .log/start-dev.log

Agents and scripts can query JSONL:

jq 'select(.event == "output" and (.messagePlain | test("error|failed"; "i")))' .log/start-dev.jsonl
jq 'select(.event == "output" and .stream == "stderr")' .log/storybook.jsonl

Output entries keep both the original ANSI-colored message and a searchable plain message.

{
  "timestamp": "2026-06-02T12:00:00.000Z",
  "label": "start-dev",
  "event": "output",
  "stream": "stderr",
  "message": "\u001b[31mfailed\u001b[39m",
  "messagePlain": "failed"
}

Rotation

Defaults:

  • max size: 10MB
  • rotated files kept: 2

Configure with CLI options:

devlog --name dev --log .log/dev.log --max-bytes 20MB --max-rotated-files 4 -- pnpm dev

Or environment variables:

DEV_SERVER_LOG_MAX_BYTES=20MB DEV_SERVER_LOG_MAX_ROTATED_FILES=4 pnpm dev

JSONL rotates only between entries, so JSON lines are not split.

Library API

import { runLoggedProcess } from 'dev-server-log'

const result = await runLoggedProcess({
  label: 'start-dev',
  command: 'pnpm',
  args: ['start:dev'],
  logPath: '.log/start-dev.log',
})

process.exitCode = result.exitCode

Publishing

Publishing is handled by GitHub Actions on v* tags.

Publishing uses npm Trusted Publishing from the publish.yml GitHub Actions workflow.