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

@shadow-garden/bapbong-contracts

v0.17.0

Published

bapbong — shared layout + plugin contracts/types (type-only deps)

Readme

@shadow-garden/bapbong-contracts

The shared vocabulary every other bapbong package speaks: paint-ready types, the plugin contract, and one small isomorphic utility (Collection). Almost all types; the only runtime code is Collection.

  • Scope: scope:pure (leaf — imports no other workspace package)
  • Depends on: prosemirror-state, prosemirror-model — type-only, for the plugin/editor-change contracts. No DOM: the package is isomorphic (runs on Node/server; enforced by a no-restricted-globals lint guard).

What it defines

  • Flow model (layout input): FlowParagraph, FlowTable / FlowTableRow / FlowTableCell, FlowFloat, and inlines InlineRun / InlineImage / InlineBreak / InlineField.
  • Resolved layout (paint-ready engine output): ResolvedLayout, ResolvedPage, LayoutLine, LayoutSegment, LayoutImageSegment, ResolvedCell, ResolvedFloat, ResolvedFootnotes, ResolvedChrome.
  • Geometry & config: PageConfig, LayoutConfig, ColumnConfig, ParagraphSpacing, ParagraphIndent, CellPadding, CaretRect, PagePoint, SelectionRect.
  • Fonts / measurement: FontSpec, FontMetrics, MeasureText, MeasureMetrics.
  • Comments: IUser, CommentNode, CommentData.
  • Plugin contract (the stable surface the editor + plugins share, so neither imports the other): EditorPlugin, PluginContext, EditorChange, RangeDecoration, PaintDecoration, EditorPointerEvent (the pointer hook + ctx.layout/ctx.setCursor let plugins hit-test tables, e.g. column resize).
  • Command contract: Command ({ name, run, isActive?, isEnabled? }) + Dispatch — the headless editor-operation surface the toolbar/menubar, plugins and a backend share. Implementations live in @shadow-garden/bapbong-commands.
  • Collection<T> — a name/id-keyed, insertion-ordered collection (get/add/remove/has/entries + iterable). Keys by id by default, or new Collection(items, { idProperty }); throws if an item lacks its key. The editor uses it as its plugin registry.

Build / test

pnpm nx build @shadow-garden/bapbong-contracts
pnpm nx test  @shadow-garden/bapbong-contracts