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

@meanhq/mean

v0.2.5

Published

Connects your web app's dev server to Mean, so annotations on your running app carry component names and source locations. Development only, one line of configuration.

Readme

@meanhq/mean

Mean is visual handoff for humans and agents. Freeze or record your screen, annotate with gestures, and hand the finished session to a human or an agent.

This package connects your web app's development server to Mean. When you mark an element of your running app, the annotation also carries its component name and source file and line, so an agent can go straight to the code. It runs in development only and adds nothing to the page.

Install

npm i --save-dev @meanhq/mean

Then connect your development server. Pick the one you use.

Vite:

// vite.config.ts
import { mean } from '@meanhq/mean/vite';
export default defineConfig({ plugins: [mean()] }); // keep your existing plugins

Next 16.3 or later, HTTP only, Webpack or Turbopack:

// next.config.mjs
import { withMean } from '@meanhq/mean/next';
export default withMean(nextConfig);

Other Node dev servers, such as webpack-dev-server, Rspack, Express or Koa:

import { createServer } from 'node:http';
import { mean } from '@meanhq/mean/middleware';

const server = createServer(app);
const middleware = mean(server, {
  dev: process.env.NODE_ENV === 'development',
  origin: 'http://127.0.0.1:3000',
  root: process.cwd(),
});
app.use(middleware); // before your routes; put middleware.scriptTag in your dev HTML

Non-Node backends, such as Rails, Django or Go:

npx @meanhq/mean --origin http://127.0.0.1:8000

Add the printed script tag to your development template only. Component HMR keeps the connection; after a dev-server restart, reload the page. The server fixtures show a complete setup for every host.

Output

An annotation on a Save button, as reported by mean inspect:

{
  "frame": 1, "n": 1, "kind": "pin", "text": "Move this button",
  "points": [[0.25, 0.36]], "region": "f1-a1-region.png",
  "element": {
    "role": "button", "label": "Save",
    "component": "SaveButton",
    "chain": ["SaveButton", "Editor", "App"],
    "source": { "file": "src/SaveButton.tsx", "line": 18, "column": 5 },
    "framework": "react",
    "elementPath": "html > body > main > button:nth-of-type(1)"
  }
}

Supported

| Framework | Component names | Source locations | | --- | --- | --- | | React | Yes | Yes, from the development JSX transform | | Vue 3 | Yes | Yes, from the template transform | | Svelte 5 | Nested components; the mounted root has no name | Yes, from the template transform | | Plain HTML | No | Static markup served by Vite |

Source locations come from the development build and are exact. A name or a location is omitted when the framework does not expose it; neither is ever inferred.

Privacy

Development only. Vite excludes the package from production builds; other servers keep it in development entry points. Loopback only. The page connects to its own development server or to the standalone relay, which connects to Mean on 127.0.0.1. Nothing leaves the machine. There are no remote requests, no telemetry and no account. Form values and editable text are never read.

Troubleshooting

Run mean doctor dom and focus the development page when prompted. It reports the connection, the matched page and whether source metadata is available.