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

@deskwork/studio

v0.14.1

Published

Editorial review studio — local web UI for the deskwork plugin

Readme

@deskwork/studio

Local web studio for the deskwork editorial-calendar plugin. Hono-backed dev server exposing the editorial dashboard, a unified review surface for longform and shortform workflows, the scrapbook viewer, and the compositor's manual.

Audience

This package backs the deskwork-studio Claude Code plugin shell. Direct npm install of @deskwork/studio into a non-deskwork host is unusual — the canonical entry point is the plugin shell, which npm installs this package on first run and dispatches via its bin shim.

If you want the editorial studio inside Claude Code, follow the marketplace install instructions at the marketplace repo. The studio plugin pairs with the lifecycle plugin (deskwork) — install both, or just the lifecycle one for headless use.

Network model

The studio binds to loopback by default (127.0.0.1) plus the local Tailscale interface when one is detected, so peers on the same tailnet can reach it via magic-DNS without any flags. There is no authentication and no rate-limiting — it is dev-only by design. Public-internet exposure stays opt-in via --host.

Routes

| Path | Surface | |---|---| | /dev/editorial-studio | Calendar dashboard across all collections | | /dev/editorial-review/<id> | Unified review surface for longform and shortform workflows | | /dev/editorial-review-shortform | Shortform desk index (per-platform composition) | | /dev/editorial-help | The compositor's manual | | /dev/scrapbook/<site>/<path> | Scrapbook viewer at any depth | | /dev/content/<site>/<project> | Bird's-eye content tree view |

Local development (deskwork monorepo)

When working on the studio itself from inside this monorepo:

npm install                                  # creates workspace symlinks
npm run dev --workspace @deskwork/studio     # Vite-in-Hono on port 47321

npm run dev boots the studio with DESKWORK_DEV=1 and tsx --watch, mounting Vite's dev middleware in front of Hono. Effects:

  • Edits under packages/studio/src/*.ts (server-side) auto-restart the process.
  • Edits under plugins/deskwork-studio/public/src/*.ts (client-side) are served by Vite with HMR — the browser auto-reloads on save (full module HMR engages whenever modules add import.meta.hot handlers).
  • The in-process esbuild step is skipped; client TS source is served directly via Vite at /src/<name>.ts.

The dev server points at the workspace root (--project-root ../..) so it reads the project's own .deskwork/config.json and surfaces the project's calendar.

Production code path (no DESKWORK_DEV) is unchanged — the studio runs the in-process esbuild on boot and serves bundled JS from .runtime-cache/dist/.

Source

Repository: audiocontrol-org/deskwork. The studio source lives at packages/studio/; shared core logic in @deskwork/core; the lifecycle CLI in @deskwork/cli.

License

GPL-3.0-or-later — same as the monorepo. See LICENSE for details.