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

@obelism/content-react

v0.4.7

Published

Obelism Content React SDK: live preview in the visual editor and rich text

Readme

Obelism Content React SDK

npm i @obelism/content @obelism/content-react

Live preview

// app/layout.tsx: starts the bridge, so blocks are selectable on every page
;<ContentBridge />

// A client component rendering an entry
;('use client')
import { editable, useLiveEntry } from '@obelism/content-react'

export const Page = ({ entry }) => {
	const { fields } = useLiveEntry(entry) // the editor's unsaved version while editing
	return fields.body.map((block) => (
		<section key={block._uid} {...editable(block)}>
			…
		</section>
	))
}
  • useLiveEntry(entry, { url? }): entry, or the editor's live version of it.
  • useContentBridge(): { isEditing, entryId, environment }, after hydration.
  • useContentBridgeEvent('saved' | 'published' | 'update', listener), e.g. router.refresh() on publish.
  • <ContentBridge url? prompt? pagePath? />: pass url only when not on content.obelism.studio; pagePath(path, locale) maps a CMS path in a locale to the site's URL for pages made with New page (default / + path).

Prompt editing

<ContentBridge /> shows editors a prompt box inside the visual editor (see @obelism/content). <ContentBridge prompt={false} /> leaves it out; useContentPrompt() gives { available, prompting, canUndo, selectedUid, prompt, createPage, undo, select } for your own UI.

Rich text

<RichText
	document={entry.fields.body}
	embeddedEntry={({ entry }) => <Card entry={entry} />}
	nodes={{ heading: ({ node, children }) => <h2>{children}</h2> }}
	marks={{
		link: ({ mark, children }) => (
			<Link href={mark.attrs.href}>{children}</Link>
		),
	}}
/>

Works in server components too (it isn't a client component).