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/core

v0.2.0

Published

Bundler-free, framework-free guts of Pointcut: client, models, drivers, and the Bridge.

Readme

@pointcut/core

The bundler-free, framework-free guts of 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.

Most users never install this directly — it comes in as a dependency of @pointcut/unplugin and @pointcut/sidecar. It's published on its own because both of those mount the same Bridge from here, so the auto-attach and sidecar paths can't diverge.

This package owns:

  • The BridgecreateBridge(), the dev-server runtime surface that turns toolbar intent into agent edits (editor-launch, agent-probe, skills-probe, and the agent run that normalizes each agent CLI's native events into a uniform NDJSON Action stream). Consumers only mount the handler.
  • Drivers — a per-agent module (claude / codex / cursor) that owns one CLI's recipe. Adding an agent is one driver plus one registry entry; the Bridge, protocol, and client never change.
  • Models — pure, framework-free authoring models (queue, locator, tokens, provenance, spacing, color, typography, copy, chat, handoff, agent-run) with injected collaborators.
  • The client — the minimal Shadow-DOM in-page toolbar (@pointcut/core/client).

A design-mode hard guard lives here: the Bridge refuses to construct unless explicitly enabled, so every consumer inherits the same gate. Pointcut never ships to production.

Install

npm install -D @pointcut/core

Entry points

import { createBridge, getDriver, DRIVERS } from '@pointcut/core';
import '@pointcut/core/client';           // the in-page toolbar (usually auto-injected)
import { /* models */ } from '@pointcut/core/models';
const handler = createBridge({ enabled: true, cwd: process.cwd() });
// mount `handler` on any Node HTTP server / dev-server middleware

See the main README for architecture and usage.

License

MIT