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

kanapa

v0.1.2

Published

A syntax highlighting code block component based on shiki for use with React Server Components

Downloads

21

Readme

kanapa

A syntax highlighting code block component based on shiki for use with React Server Components!

[!IMPORTANT] This library is only supported within React Server Components, it may work in other environments but they will not be officially supported at this time!

Getting Started:

bun add kanapa

Usage:

import { Code } from "kanapa";

async function MyServerComponent() {
  return (
    <div>
      <Code
        lang="json"
        code={`{
  "someKey": "someValue"
}`}
      />
    </div>
  );
}

Exports:

  • Code - A highlighted code block component
    • Props:
      • code?: string - the code to be highlighted
      • children?: string - alternative to the code prop, code to be highlighted (if both code and children are provided, the code prop will win out)
      • lang: string - the language of the code, used for syntax highlighting, see supported languages
      • theme?: string - an optional theme override for the code block, this will no longer render the "fallback" themed code block, see supported themes
      • className?: string - an optional classname to apply to a wrapping element
  • MDXCode - A highlighted code block component meant for use within transformed mdx (see #mdx for more details)
    • Props:
      • children: ReactElement - the code react element to be highlighted
      • className?: string - An optional classname to apply to the wrapping element
  • updateConfig - a function to update the config for all Code and MDXCode components
    • Arguments:
      • newConfig: Config - the new config to set
  • config - a live binding to the current config object

Config:

This library supports a runtime config with the following options:

  • themes: Record<'light' | 'dark', string> - an object map of light and dark themes to use for code blocks
  • selectors: 'system' | Record<'light' | 'dark', string> - the type of selectors to use to pick between the light or dark themed code block

Example configs:

updateConfig({
  themes: {
    light: 'github-light',
    dark: 'github-dark',
  },
  // Uses media queries to pick the current desired user theme
  selectors: 'system',
});

updateConfig({
  themes: {
    light: 'vitesse-light',
    dark: 'vitesse-dark'
  },
  selectors: {
    light: 'html.light',
    dark: 'html.dark',
  },
})

MDX:

If you're rendering code blocks from mdx content, then you'll want to use the MDXCode export. Additionally I recommend using the rehype-mdx-code-props rehype plugin to automatically extract metadata on the code block and pass it as props to the code element (e.g. for passing the language down to the code block).

For frameworks that expose a mdx-components.tsx file (e.g. Next.js's @next/mdx setup), you'll want to map the 'pre' html element to the MDXCode component, e.g.:

// mdx-components.tsx

export function useMDXComponents() {
  return {
    pre: MDXCode
  }
}

Contributing:

Building:

This library uses swc and TypeScript to build the source code and generate types.

To build the library, run bun run build from the root, or from this workspace!

Code Quality:

Type Checking:

This library uses TypeScript to perform type checks, run bun run type-check from the root or from this workspace!

Linting

This library uses BiomeJS for linting, run bun run lint from the root or from this workspace!

Tests

This library uses Bun for running unit tests, run bun run test from the root or from this workspace!

Publishing:

To publish the library, run bun run pub from the workspace root. This will prompt you to login to npm and publish the package.

Note: In the future, we will automate this process using GitHub Actions. And also add in tooling to manage releases / changelogs!