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

@eventcatalog/editor

v0.1.2

Published

Rich editor for EventCatalog resources.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

boyney123boyney123

Keywords

Readme

@eventcatalog/editor

A local-first rich editor for EventCatalog resources. Run it from a catalog, pass a catalog path, or open the editor and mount one from the UI.

Usage

npx @eventcatalog/editor

The editor opens http://localhost:3900 in your browser. Startup uses this order:

  1. Use --catalog <path> when provided.
  2. Use the current directory when it contains eventcatalog.config.js.
  3. Use the first immediate child directory that contains eventcatalog.config.js, ignoring .eventcatalog-core.
  4. Show a catalog path screen when no catalog can be found.

Flags

  • --catalog <path> — EventCatalog root to edit; omit it to use the current directory or choose a catalog in the UI
  • --port <n> — port to listen on (default: 3900)
  • --no-open — do not open the browser
  • --help, -h — show help
  • --version, -v — show version

Requirements

  • Node 22+
  • An EventCatalog directory containing an eventcatalog.config.js

What works today (0.1.0)

  • Browse every resource type (services, domains, events, commands, queries, channels, entities, flows, users, teams).
  • Edit markdown bodies in a rich Tiptap editor.
  • Edit simple frontmatter fields (strings, string arrays).
  • Full-text search across names, summaries, bodies, and frontmatter (MiniSearch, prefix + fuzzy).
  • Delete resources (with confirmation).
  • Last-write-wins conflict detection via mtime (returns 409 on stale save).
  • MDX components round-trip verbatim as opaque blocks.

What's coming

See ROADMAP.md.

Architecture

Two seams make the editor data-source-agnostic:

  1. CatalogStore interface on the server — v1 ships a LocalSdkStore adapter that wraps @eventcatalog/sdk. Future adapters (GitHub, DB, remote API) slot in without touching UI or routes.
  2. /api/resources/:type/:id[/:version] HTTP contract — resource-oriented, keyed by { type, id, version }, never by file path. UI talks only to this contract.

Development

npm install
npm run dev       # server on :3900 mounted to /Users/dboyne/Dev/eventcatalog/tmp/my-catalog + Vite on :5173
npm test
npm run build     # UI build + server bundle

License

MIT