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

@ledric/gui

v0.4.0

Published

ledric admin GUI — React via CDN, served by @ledric/http-server.

Downloads

120

Readme

@ledric/gui

Static admin UI for ledric. React + Tailwind, served by @ledric/http-server, no bundler — every dependency loads from a CDN at runtime via an importmap.

What's in here

src/index.ts        single export: guiAssetsPath (absolute path to web/)
web/index.html      Tailwind Play CDN + esm.sh importmap + <div id="root">
web/app.js          React app entry: routing + layout
web/lib/api.js      fetch wrapper for the ledric HTTP API (same origin)
web/components/
  TypeList.js       /types — every content type with entry counts
  EntryList.js      /types/:type — table of entries using summary_fields
  EntryEditor.js    /types/:type/new and /types/:type/:slug — author + publish
  fields.js         per-field-type renderers (string/markdown/asset/…)

The package ships dist/ + web/. dist/ is the tiny TS export; web/ is served verbatim by @fastify/static.

Running it

npx ledric http --gui
# admin GUI at http://127.0.0.1:3000/admin

--gui-mount <path> to change the mount, --gui-path <dir> to point at a fork of the assets.

Why CDN + no bundler

This is an admin UI for the local dev loop. Iteration is "save and refresh the browser." A bundler buys nothing and slows the inner loop.

  • React 18 via esm.sh
  • React Router via esm.sh (deps pinned to react@18)
  • htm for tagged-template JSX
  • Tailwind via Play CDN — runtime JIT, ~50 ms first-paint cost on localhost

If/when these deps need to be vendored (offline support, custom Tailwind config, TS for the React side), the migration is "swap the importmap for a build step." Nothing else changes.

Field renderers

Dispatched from field.type in fields.js. A new field type means one new case in FieldRenderer and one component below it. Today's coverage:

| Field type | Renderer | |---|---| | string | input or textarea (depending on max) | | slug | input + "derive" button (uses from) | | number | number input with min / max / integer step | | boolean | checkbox | | date | date picker (ISO YYYY-MM-DD) | | markdown | textarea, monospace, max enforced | | enum | select | | asset | thumbnail + file picker (uploads via POST /assets) | | references | read-only id list (autocomplete is v2) | | array of string | tags input | | anything else | read-only JSON view |

Auth

There isn't any. Requests under /admin and to /rpc are all unauthenticated. Bind ledric to 127.0.0.1 (the default) and you're fine on a dev machine; binding to a public interface with --gui will print a loud warning but won't block the user. Real auth lands in a follow-up.