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

@devframes/plugin-git

v0.7.2

Published

Git integration for devframe — a read-only repository dashboard (status, log, branches, diff) with a Next.js + shadcn/ui SPA over type-safe RPC.

Readme

@devframes/plugin-git

[!WARNING] Experimental This plugin is experimental and may change without a major version bump until it stabilizes.

Git integration for devframe — a repository dashboard with a Next.js App Router + shadcn/ui SPA over type-safe RPC. The host process shells out to git and exposes the repository; the same bundle runs as a live dev server or a fully static deployment.

Status, a SourceTree-style commit graph, branches, and diffs are read-only; staging, unstaging, and committing are available when write mode is enabled. The UI follows the system light/dark preference with a manual toggle.

Install

npm i -D @devframes/plugin-git

Standalone CLI

Run the dashboard against the current repository:

npx devframe-git              # dev server (live RPC over WebSocket)
npx devframe-git --write      # also enable staging / committing from the UI
npx devframe-git build        # static deploy → dist-static/
npx devframe-git --port 4000

Programmatic

createGitDevframe(options) returns a devframe definition you can mount into any host with devframe's adapters, or drive yourself.

import { createGitDevframe } from '@devframes/plugin-git'
import { createCac } from 'devframe/adapters/cac'

await createCac(createGitDevframe({ repoRoot: process.cwd() })).parse()

| Option | Default | Description | |--------|---------|-------------| | repoRoot | the devframe cwd | Repository directory to inspect. | | basePath | adapter-resolved | Mount path (/ standalone, /__git/ hosted). | | distDir | bundled SPA | Override the served SPA directory. | | port | 9710 | Preferred dev-server port. | | write | false | Enable staging, unstaging, and committing from the UI. |

RPC surface

The read functions are each a query with snapshot: true: resolved live over WebSocket in dev, and served from a snapshot baked at build time for static deploys. Each degrades to an empty, isRepo: false result outside a git repository.

  • git:status — branch, upstream tracking (ahead/behind), staged / unstaged / untracked files, parsed from git status --porcelain=v2. Reports canWrite.
  • git:log — paginated commit history (limit / skip) including parent hashes, which drive the commit graph.
  • git:branches — local branches with SHA, upstream, ahead/behind, tip subject.
  • git:diff — per-file added/deleted counts for the working tree or index, plus a unified patch for a selected file.

Write actions are action functions, registered only when write mode is enabled (createGitDevframe({ write: true }) or the --write flag) and gated behind status.canWrite in the UI. Each returns fresh status (commit returns a result):

  • git:stagegit add the given paths.
  • git:unstagegit restore --staged the given paths.
  • git:commit — commit the staged changes with a message.

Develop

pnpm -C plugins/git dev     # client (Next.js HMR) + RPC backend together
pnpm -C plugins/git build   # tsdown (node) + next build (SPA) → dist/

pnpm dev starts the Next.js dev server (with hot-reload) and the devframe RPC/WebSocket backend at the same time, then prints both URLs — open the UI one. The SPA connects to the backend over the WebSocket port carried in NEXT_PUBLIC_DEVFRAME_WS. Override ports with PORT (UI) and DEVFRAME_GIT_PORT (backend). Run a single side with dev:client or dev:server.

The SPA is a standard shadcn/ui setup (Tailwind v4, components/ui/*). Three Next.js settings in src/client/next.config.mjs keep it portable: output: 'export' (devframe owns the server), assetPrefix: '.' (relative assets so the same bundle works at any base), and trailingSlash: true (composes with devframe's static directory-with-index resolution).