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

@pointcut/unplugin

v0.1.1

Published

Universal transform/inject + dev-server auto-attach for Pointcut, across all bundlers via unplugin.

Readme

@pointcut/unplugin

The universal build-time plugin for Pointcut — a dev-only, design-mode-gated in-browser toolbar where you point at a live DOM element and the intended change is cut into source by an AI coding agent.

This package does two genuinely bundler-agnostic jobs on the transform side, plus a thin per-dev-server auto-attach:

  1. Source Stamp — writes data-pointcut-loc="file:line:col" onto every opening element tag (via a pluggable per-framework stamper: Vue SFC, JSX/TSX, Svelte, plain HTML), so a clicked DOM node resolves back to its exact spot in source.
  2. Inject — auto-prepends import '@pointcut/core/client' into the entry (opt out with inject: false and import it yourself).
  3. Auto-attach — where a dev server exists (Vite / Webpack / Rspack), mounts the Bridge so toolbar intent becomes agent edits. For bundlers without a dev-server hook (standalone esbuild / Rollup / Rolldown / Farm), pair this with @pointcut/sidecar.

Pointcut is dev-only. The plugin carries a hard guard (apply: 'serve') and is inert unless you explicitly opt it into your config behind your own dev condition. It never ships to production.

Install

npm install -D @pointcut/unplugin
# or
pnpm add -D @pointcut/unplugin

Quick start (Vite)

Import the plugin from the subpath matching your bundler and gate it behind a dev flag:

// vite.config.js
import { defineConfig } from 'vite';
import pointcut from '@pointcut/unplugin/vite';

export default defineConfig({
  plugins: [
    // Only active when you opt in — e.g. `DESIGN=1 vite`.
    process.env.DESIGN ? pointcut({ framework: 'auto' }) : null,
  ],
});

Bundler entry points

Import from the subpath for your bundler:

import pointcut from '@pointcut/unplugin/vite';
import pointcut from '@pointcut/unplugin/webpack';
import pointcut from '@pointcut/unplugin/rspack';
import pointcut from '@pointcut/unplugin/esbuild';
import pointcut from '@pointcut/unplugin/rollup';
import pointcut from '@pointcut/unplugin/farm';

Options

pointcut({
  framework: 'auto',          // 'auto' | 'vue' | 'jsx' | 'svelte' | 'html'
  inject: true,               // auto-inject the client; false to import it yourself
  agents: 'auto',             // agent allow-list, or 'auto' for every CLI on PATH
  bridge: { port: 7321 },     // stamped into the client as its Bridge base URL
  tokens: { /* … */ },        // optional design-token grouping hints (zero-config works)
});

For setups with no dev-server middleware hook (standalone esbuild / Rollup / Rolldown / Farm), set inject: false, point bridge.port at your sidecar, and run npx pointcut-sidecar alongside the build.

See the main README for full per-bundler examples and architecture.

License

MIT