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

@ilieberacha/clite-overlay

v0.1.0

Published

A dev-only browser overlay that captures UI, network, console, storage, and source context into AI-ready packets.

Readme

Clite

Clite is a dev-only browser overlay for sending precise app context to AI coding agents. Install it in a local web app, click the floating CLITE button, inspect any point on the screen, add a short note, then copy a Markdown or JSON packet with the selected UI, source metadata, console logs, network requests, storage, performance entries, route changes, and recent interaction timeline.

It is built for the workflow where "this button is broken" is not enough. The packet gives the agent the DOM target, surrounding component metadata, the requests that just happened, the console output, and the exact context note in one paste.

Install

npm install @ilieberacha/clite-overlay --save-dev

Use it only in development builds.

import { createClite } from "@ilieberacha/clite-overlay";

if (import.meta.env.DEV) {
  createClite({
    app: {
      name: "Dashboard",
      version: import.meta.env.VITE_APP_VERSION,
      environment: import.meta.env.MODE
    }
  });
}

React and Vite Source Metadata

Clite can read source metadata from data-clite-* attributes. For React projects using @vitejs/plugin-react, add the Babel plugin in development:

import react from "@vitejs/plugin-react";
import { defineConfig } from "vite";

export default defineConfig(({ mode }) => ({
  plugins: [
    react({
      babel: {
        plugins: mode === "development" ? ["@ilieberacha/clite-overlay/babel"] : []
      }
    })
  ]
}));

The plugin adds:

data-clite-component="SaveButton"
data-clite-source="/absolute/path/src/SaveButton.tsx"
data-clite-line="18"
data-clite-column="10"

Manual annotations also work in any framework:

<button
  data-clite-component="SaveButton"
  data-clite-source="/src/features/settings/SaveButton.tsx"
  data-clite-line="42"
>
  Save
</button>

Capture Surface

Clite captures:

  • Selected element selector, role, accessible name, text preview, attributes, rect, computed styles, and sanitized HTML preview.
  • Source metadata from the selected element and annotated ancestors.
  • fetch and XMLHttpRequest method, URL, status, duration, headers, request body preview, and response body preview.
  • Console debug, info, log, warn, and error calls with stack context.
  • Runtime errors and unhandled promise rejections.
  • Click, input, and route timeline.
  • localStorage, sessionStorage, navigation timing, and recent resource timing.
  • Custom context added through addContext().

Sensitive keys, auth headers, bearer/basic tokens, common OAuth parameters, cookies, passwords, API keys, and session-like fields are redacted by default.

API

const clite = createClite({
  enabled: true,
  app: { name: "Billing", environment: "development" },
  maxEvents: 250,
  maxNetworkEntries: 80,
  maxConsoleEntries: 120,
  maxBodyBytes: 4000,
  redaction: {
    keys: ["tenantSecret"],
    urlParams: ["signed_url"],
    patterns: [/internal-[a-z0-9]+/gi]
  },
  capture: {
    fetch: true,
    xhr: true,
    console: true,
    errors: true,
    clicks: true,
    inputs: true,
    route: true,
    storage: true,
    performance: true
  },
  ui: {
    startOpen: false,
    shortcuts: true,
    position: "bottom-right"
  }
});

clite.addContext("currentAccount", { id: "acct_123" });
clite.mark("Opened settings");
clite.inspect();
const packet = clite.capturePacket("Save button is expected to POST /api/profile.");
await clite.copyMarkdown();

Keyboard

  • Alt+Shift+C: open the overlay.
  • Alt+Shift+I: enter inspect mode.
  • Escape: cancel inspect mode.

Demo

npm install
npm run dev

Open the printed local URL, click CLITE, use Inspect, then click the demo form or action buttons.

Privacy Model

Clite is local-first. It does not send packets anywhere. Copy and download actions are user-triggered. Keep it out of production builds, and add project-specific redaction rules for domain secrets.

For details, see docs/privacy.md.

clite