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

@mr-akami/kilog

v2026.818.1

Published

kilog — dev-time structured logging toolkit (CLI, web UI, runtime + framework integrations)

Readme

@mr-akami/kilog

Let your AI agent search your browser and Node.js logs in one command.

kilog captures console, fetch, and uncaught errors during development into a per-project .kilog/ directory. Point the CLI (or web UI) at any directory and it searches every .kilog/ beneath it — you pick the scope, nothing is centralized.

npm i -D @mr-akami/kilog

One package: the kilog CLI, the web UI, and every framework integration.

Instrument

Node — no code changes:

{ "scripts": { "dev": "node --import @mr-akami/kilog/register ./src/index.ts" } }

Vite:

import kilogPlugin from "@mr-akami/kilog/vite-plugin";
export default defineConfig({ plugins: [kilogPlugin()] });

Next.js (App or Pages Router):

import { withKilog } from "@mr-akami/kilog/nextjs-plugin";
export default withKilog({
  /* your next config */
});

Cloudflare Workers (wrangler dev):

import kilogWranglerPlugin from "@mr-akami/kilog/wrangler-plugin";
export default defineConfig({ plugins: [cloudflare(), kilogWranglerPlugin()] });

Read

kilog logs -f                    # follow, docker-logs-style flags
kilog logs --since 10m -n 100
kilog logs --level error | rg timeout
kilog sql "select level, count(*) from logs group by 1"
kilog stats
kilog ui                         # browser UI on :3210
kilog doctor                     # is anything actually being captured?

logs also takes --until, --runtime, --project, and --json.

Entry points

| Import | What | | --------------------------------- | ----------------------------------------------- | | @mr-akami/kilog | storage / discovery / index / query primitives | | @mr-akami/kilog/register | auto-register hook (Node / Bun / Deno dispatch) | | @mr-akami/kilog/runtime-node | Node runtime instrumentation | | @mr-akami/kilog/vite-plugin | Vite plugin | | @mr-akami/kilog/nextjs-plugin | Next.js plugin | | @mr-akami/kilog/wrangler-plugin | Cloudflare Wrangler dev integration | | @mr-akami/kilog/web-ui | Hono server + DuckDB-wasm browser UI |

Logs are JSONL under .kilog/raw/, indexed into DuckDB — nothing leaves your machine.

Previously published as the @kilog/* scoped packages; those are deprecated.

Full docs: https://github.com/Mr-akami/kilog

MIT