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

logjar

v0.0.0-pre.1

Published

Unified frontend + backend log capture for dev environments. Run `logjar -- your-command` to intercept all logs into a single rolling file that coding agents can read.

Downloads

128

Readme

Logjar

Unified frontend + backend log capture for dev environments. A single rolling log file that coding agents (Claude, Cursor, Copilot, etc.) can read to understand what's happening in your app.

The Problem

When a coding agent is helping you debug, it can't see your terminal output or browser console. You end up copy-pasting error messages back and forth. Logjar fixes this by writing all logs — backend stdout/stderr and frontend console output — into one small, rolling file the agent can read directly.

Quick Start

npm install logjar --save-dev

1. Wrap your dev command

# Before
turbo run dev --parallel

# After
npx logjar -- turbo run dev --parallel

That's it for the backend. All stdout/stderr from your command is captured.

2. Add frontend capture

Choose one of these options:

Option A — ES module import (React, Vue, Svelte, etc.)

// Add to your app's entry point (e.g., main.ts, _app.tsx)
import "logjar/client";

// Or initialize with custom options
import { initLogjar } from "logjar/client";
initLogjar({ app: "web", levels: ["log", "info", "warn", "error", "debug"] });

Option B — Script tag

<script src="./node_modules/logjar/src/client/snippet.js"></script>

Option C — Conditional (only in dev)

if (process.env.NODE_ENV === "development") {
  import("logjar/client");
}

Option D — Chrome/Chromium extension (no app code changes)

If you do not want to import logjar/client into the app, you can use the optional browser extension instead. Download the latest asset from GitHub Releases, extract it, then load it locally:

  1. Open chrome://extensions.
  2. Turn on Developer mode.
  3. Click Load unpacked.
  4. Select the extracted extension folder.

Then start Logjar locally, open your app in the browser, click the Logjar extension, confirm the port matches your CLI process (default 8797), and enable Capture this tab.

The extension captures browser logs for the current tab and forwards them to your local Logjar server. This is useful when you want frontend capture without changing application code.

3. Tell your coding agent

Add the following to your AGENTS.md / CLAUDE.md / .cursorrules:

Read .logjar/logs.txt to check for frontend and backend errors.

4. Update your .gitignore

Update your .gitignore to exclude the logjar directory:

.logjar

CLI Options

logjar [options] -- <command>

Options:
  --port <n>       HTTP port for frontend logs  (default: 8797)
  --out <path>     Log file path                (default: .logjar/logs.txt)
  --max-age <s>    Rolling window in seconds    (default: 900)
  --max-size <kb>  Max log file size in KB      (default: 200)

Examples

# Custom port and output
logjar --port 9000 --out logs/dev.txt -- npm run dev

# Longer window, bigger cap
logjar --max-age 600 --max-size 100 -- next dev

# Add to package.json scripts
{
  "scripts": {
    "dev": "logjar -- turbo run dev --parallel"
  }
}

License

MIT