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 🙏

© 2024 – Pkg Stats / Ryan Hefner

react-components-in-markdown

v0.1.5

Published

Render custom React components in Markdown

Downloads

6

Readme

react-in-markdown

Updated react-in-markdown from Kitze.io - added JSON/JSObject support in params.

⚠️ Warning: This is not a standalone library, it should be used along with the markdown-to-react-components library

What does it do?

This library allows you to render custom React Components when writing Markdown, using a special syntax.

[emoji]({"code": "fire", "size": 35})
or
[emoji]({code: "fire", size: 35})

This will render the emoji component, with {code:"fire", size:"35"} as props.

How does rendering Markdown to React work?

In order to render Markdown to React components you should use the markdown-to-react-components library. Under the hood it's really simple, it uses marked to parse a string that contains Markdown, and it returns back React components.

The cool thing about the MTRC library is the configure method which can customize the output of the components. An example:

import MTRC from 'markdown-to-react-components';

MTRC.configure({
  h1: React.createClass({
    render() {
      return <h1 id={this.props.id} style={{color: 'red'}}>{this.props.children}</h1>
    }
  })
});

How to use react-in-markdown

In order to render custom React components inside of Markdown, you should plug the renderCustomComponents method into the configuration of the a element:

import MTRC from 'markdown-to-react-components';
import {renderCustomComponents} from 'react-in-markdown';

const customComponents = {
	emoji: ({code,size}) => <div style={{fontSize:size}}> {code} </div>,
	awesomeHeader: ({size=22, children}) => <h1> style={{fontSize:size}}>children </h1>
};

MTRC.configure({
  a: props => renderCustomComponents(props, customComponents)
});

So when the parser finds the anchor syntax [emoji]({ code: "fire", size: 35}) it will try to check if emoji is a key in our customComponents object. In this case, emoji is a key in our customComponents object, so it will render that component with the props.

But if we have a regular link like [Kitze.io](http://kitze.io), it will see that Kitze.io isn't a key in the customComponents object so it will just render a regular link 👉 Kitze.io