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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@frfla/react-md-renderer

v0.250829.0

Published

markdown renderer with react

Readme

@frfla/react-md-renderer

Markdown Renderer With CSS-Only Customs

npm install @frfla/react-md-renderer
yarn add @frfla/react-md-renderer
pnpm add @frfla/react-md-renderer

Quick Start

 <Renderer
      markdown={`# React\n## Markdown Renderer\n**Bold Text** Plain Text`}
      CSS={{
        h2: {
          fontFamily: 'serif',
        },
        pre: {...},
        img: {...},
      }}
  />

API/Props

markdown

markdown: string
  • Markdown Text (Plain Text)

CSS

CSS: {
  [markup]: string|CSS
}
  • a, blockquote, checkbox, code, pre, h1-h6, hr, img, li, ol, ul, p, table, strike, strong, italic
  • CSS is injected into the corresponding markup using a KEY.
    • It can be provided as a string. In this case, it works identically with className.
  • By default, it is not dependent on any CSS library.
...
  CSS={
    { h1: { color : 'blue', fontWeight: '700'  },
      h2: 'className',
      p: CSS_VAR }
  }
...

classNamePrefix

classNamePrefix?: string
  • When CSS is defined externally without injection (e.g. module CSS), you can apply a prefix.
  • In this case, classNames are assigned in the format prefix-h1, prefix-h2;
  • If no prefix is provided, each tag automatically receives a className such as md-renderer-h1.
  • When the CSS prop is injected, the prefix is ignored.

adjustHeadings

classNamePrefix?: string

If true, in a document, the h1 tag should exist as the single main heading. Here’s how to adjust it:

  • default: false
  • If there are multiple h1 tags, change the additional ones to h2. Subsequent headings should be adjusted accordingly (h3 to h6).
  • The styling applied to the original h1 should be retained. This means keeping the styling that makes it appear as a primary heading while optimizing the document’s structure by adjusting the markup.