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

@glyphrogue/editor

v0.1.0

Published

Glyphrogue's dev-time authoring tools: map editor, tileset/font-calibration editor, content browser, composition wizard, config UI, and hot-reload harness.

Readme

@glyphrogue/editor

Dev-time companion tooling: map editor, tileset/calibration editor, content browser, behavior wizard, config UI, and the hot-reload dev harness they all mount inside. @glyphrogue/core is a peerDependency — the editor operates on whatever live api/world the consuming game already built, never constructing its own instance. Never imported by a game's production build.

Authored in Svelte 5, compiled ahead of time — dist/ (built via npm run build) is the only thing published; .svelte source and the Svelte compiler are dev-time only. See ../../docs/design/editor.md for the full design and ../../BACKLOG.md's "packages/editor design roadmap" for implementation sequencing.

Usage

import { mountEditor } from '@glyphrogue/editor';

mountEditor(document.getElementById('editor-root'), api);

Hot-reload state preservation and the shared file-write API are separate, opt-in pieces a consuming game's own dev bootstrap/vite.config.js wires up (see ../../docs/design/editor.md's "hot-reload dev harness" and "shared file-write API" sections):

// dev bootstrap (alongside mountEditor above)
import { snapshotWorld, restoreWorldFromSnapshot } from '@glyphrogue/editor/hotReload';

// vite.config.js
import { createFileWriteApi } from '@glyphrogue/editor/devServerPlugin';
export default {
  plugins: [createFileWriteApi({ projectRoot: __dirname })],
};

Status

Harness foundation (item 2, session 29), plugin management (item 3, session 32), shared UI infrastructure (item 4, session 33), the map editor's standalone-authoring scope (item 5, session 34), the generator composition tool (item 6, session 36), the content browser (item 7, session 37), the behavior wizard (item 8, session 38), the tileset/ font-calibration editor (item 9, session 39), and config UI (item 10, session 40) are all complete — every item in the packages/editor design roadmap is now implemented. Map editor in-context editing/override export remains deferred out of item 5 (packages/core has no "current zone" concept to build it against yet) — see ../../BACKLOG.md's "packages/ editor design roadmap".