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

lookman

v2.0.0

Published

A smarter console.log() for JavaScript. Debug values, detect changes, trace async operations, track mutations, and measure performance.

Readme

 _                 _
| | ___   ___ | | ___ __ ___   __ _ _ __
| |/ _ \ / _ \| |/ / '_ ` _ \ / _` | '_ \
| | (_) | (_) |   <| | | | | | (_| | | | |
|_|\___/ \___/|_|\_\_| |_| |_|\__,_|_| |_|

Lookman

A smarter console.log() for JavaScript.

Debug values, detect changes, trace async operations, track mutations, and measure performance.

npm install lookman
import { dbg } from 'lookman';

const user = dbg(await fetchUser(123), 'user');
 DBG  users/service.ts:42 in getUser()
  user [Object] {
    "id": 123,
    "name": "Gurjot"
  }

Why Lookman?

console.log tells you a value. It does not tell you what changed, where it changed, who changed it, or how long an async call took.

Lookman sits between ad-hoc logging and full observability:

console.log()
      ↓
Lookman          ← you are here
      ↓
Structured Logging
      ↓
Full Observability Platforms

It is a developer debugging and runtime inspection toolkit — not a replacement for Pino, Winston, or Sentry.


Comparison

| Feature | console.log | Lookman | | ----------------- | ----------- | ------- | | Value logging | Yes | Yes | | Source location | No | Yes | | Change detection | No | Yes | | Promise tracking | No | Yes | | Execution timing | No | Yes | | Mutation tracking | No | Yes | | Counters | No | Yes | | Object watching | No | Yes | | Structured JSON | No | Yes |


Quick start

import { dbg } from 'lookman';

// Inline value inspection (returns the same value)
const total = dbg(cart.reduce((s, i) => s + i.price, 0), 'total');

// Promises
const user = await dbg(fetchUser(id), 'user');

// Mutations — who changed it?
const state = dbg.track({ user: { name: 'Gurjot' } }, 'state');
state.user.name = 'John';
// ⚡ TRACK  state.user.name  "Gurjot" → "John"

Disable in production:

dbg.enabled = false;
// or LOOKMAN_ENABLED=false

Core API

| API | Purpose | | --- | --- | | dbg(value, label?) | Log value + location + change detection | | dbg.count(label?) | Call counter | | dbg.time / dbg.timeEnd | Elapsed timing | | dbg.group / dbg.groupEnd | Indent related logs | | dbg.table(data, label?) | console.table with location | | dbg.watch(obj, label?) | Proxy-based deep mutation watch | | dbg.track(obj, label?) | In-place deep mutation track | | dbg.log(...args) | console.log with location | | dbg.silent(value, label?) | Log only when value changes | | dbg.diff(prev, curr) | Structured value diff | | dbg.assert(cond, msg?) | Debug assertion | | dbg.once(key, value, label?) | Log once per key | | dbg.fn(fn, label?) | Trace sync/async functions | | dbg.configure(options) | Runtime configuration | | dbg.reset() | Clear history / counters / once keys | | dbg.enabled | Global on/off |

Full reference: docs/core-api.md


Mutation hook

Your JavaScript object changed. But who changed it?

const state = dbg.track({ user: { name: 'Gurjot' } }, 'state');
state.user.name = 'John';
⚡ TRACK

state.user.name
"Gurjot" → "John"

Location:
app.ts:12

Configuration

dbg.configure({
  enabled: true,
  colors: true,
  timestamps: false,
  location: true,
  format: 'pretty', // or 'json'
});

Environment variables: LOOKMAN_ENABLED, LOOKMAN_FORMAT, LOOKMAN_COLORS, LOOKMAN_TIMESTAMPS, LOOKMAN_LOCATION.

See docs/configuration.md.


TypeScript

const user = dbg(user); // type preserved
const watched = dbg.watch(user, 'user'); // same type

Framework notes

Works in Node.js 18+, Bun, and modern bundlers (Vite, Next.js, React apps) when running in Node or browser-like environments that provide console and Error.stack. Browser support uses the same API; colors depend on the console.


Performance

When disabled, Lookman returns early before stack parsing, serialization, or Proxy work.

Run local micro-benchmarks:

npm run bench

Do not treat micro-benchmarks as absolute truth — measure in your app.


Documentation

Examples live in examples/.


License

MIT © Gurjot Saini