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

@oxa/react

v0.0.2

Published

React components for rendering OXA documents

Readme

@oxa/react

React components for rendering OXA documents.

Installation

npm install @oxa/react

Usage

import { OxaProvider, OXA, defaultRenderers } from "@oxa/react";

const document = {
  type: "Document",
  children: [
    {
      type: "Paragraph",
      children: [{ type: "Text", value: "Hello, world!" }],
    },
  ],
};

function App() {
  return (
    <OxaProvider renderers={defaultRenderers}>
      <OXA ast={document} />
    </OxaProvider>
  );
}

Adding Styles

This package uses Tailwind CSS for default styling. To include the styles in your application, add @oxa/react as a source in your CSS:

@import "tailwindcss";
@source "../node_modules/@oxa/react/dist";

The @source directive tells Tailwind v4 to scan the package's dist files for class names. See the Tailwind CSS docs on content configuration for more details.

Custom Renderers

You can override any node renderer by passing a renderers prop to <OxaProvider>:

import { OxaProvider, OXA } from "@oxa/react";
import type { OxaNode } from "@oxa/react";

function CustomHeading({ node }: { node: OxaNode & { level?: number } }) {
  return <h1 style={{ color: "blue" }}>{node.children?.map(/* ... */)}</h1>;
}

function App() {
  return (
    <OxaProvider renderers={{ Heading: CustomHeading }}>
      <OXA ast={document} />
    </OxaProvider>
  );
}

Custom renderers are merged with the defaults — you only need to provide the ones you want to override.

Merging Renderers

Use mergeRenderers to combine multiple renderer sets:

import { mergeRenderers, defaultRenderers } from "@oxa/react";

const myRenderers = mergeRenderers([defaultRenderers, customRenderers]);

Renderers later in the array take precedence.

This package was inspired by the myst-to-react package.