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

@avocadostudio-ai/blocks

v0.21.1

Published

Built-in React block renderers and block catalogue for Avocado Studio

Readme

@avocadostudio-ai/blocks

The built-in React renderers for Avocado Studio's block set, plus the dispatch layer that lets you replace any of them with your own component.

Install

npm install @avocadostudio-ai/blocks
import { SharedBlockRenderer } from "@avocadostudio-ai/blocks"
import "@avocadostudio-ai/blocks/styles.css"

export function Page({ page }) {
  return page.blocks.map((block) => <SharedBlockRenderer key={block.id} block={block} />)
}

The stylesheet is not optional — every renderer is styled by it.

The block set

Twenty types, all schema-declared in @avocadostudio-ai/shared:

Hero, FeatureGrid, Testimonials, FAQAccordion, CTA, Card, CardGrid, RichText, Banner, Carousel, Embed, Footer, Gallery, Quote, SiteHeader, Stats, Table, Tabs, TwoColumn, Video.

SiteHeader and Footer are chrome: structurally pinned, always present, and not addable, movable or removable from the editor.

rendererTypes is the live list, so you never have to keep a copy of it.

Using your own component for a type

import { registerCustomRenderer } from "@avocadostudio-ai/blocks"

registerCustomRenderer("Hero", MyHero)

SharedBlockRenderer looks the type up and falls back to the built-in when nothing is registered. hasRenderer and getCustomRenderer let you check.

Ordering matters and it bites: a globalThis registry override must be last in source order, or a transitive import re-registers the default on top of yours. If your host bundles across RSC / SSR / route-handler layers, do not rely on module order at all — pass the registration through the registerBlocks hook on createEditorApiHandler / createOrchestrator, which re-runs it after the built-ins have registered.

Rendering with your own block set entirely

You do not need this package. A site with its own components renders them itself and describes them to the editor with a block manifest. This package is the starter kit, not the contract.

Exports

| Import | What it provides | |---|---| | @avocadostudio-ai/blocks | SharedBlockRenderer, registerCustomRenderer, hasRenderer, getCustomRenderer, BlockCatalogue, BlocksHydrator, BlockErrorBoundary, rendererTypes | | .../styles.css | The stylesheet every renderer needs |

Peers

next >= 15, react >= 19, react-dom >= 19.

License

Apache-2.0