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

@trieuvi/react-showdown

v1.6.1

Published

Render React components within markdown and markdown as React components!

Downloads

2

Readme

react-showdown Build status Test coverage Dependency Status

Render React components within markdown and markdown as React components!

Features

Installation

npm install --save react-showdown

Use as React component

Really simple markdown example with ES6/JSX:

import { Markdown } from 'react-showdown';

render: () => {
    var markdown = '# Hello\n\nMore content...';
    return <Markdown markup={ markdown } />
}

Use a React component and use it within the markdown with ES6/JSX:

import { Markdown } from 'react-showdown';

const MyComponent extends Component {
	render() {
		return React.createElement(this.props.tag, null, this.props.children);
	}
};

render: () => {
    var markdown = '# Hello\n\n<MyComponent tag="strong">More Content...</MyComponent>';
    return <Markdown markup={ markdown } components={{ MyComponent }} />
}

Use the converter

Really simple markdown example:

var Converter = require('react-showdown').Converter;
var converter = new Converter();

var markdown = '# Hello\n\nMore content...';
var reactElement = converter.convert(markdown);

Use a React component and use it within the markdown:

var createClass = require('create-react-class');
var MyComponent = createClass({
	render: function() {
		return React.createElement(this.props.tag, null, this.props.children);
	}
});

var Converter = require('react-showdown').Converter;
var converter = new ReactShowdown.Converter({ components: { 'MyComponent': MyComponent }});

var markdown = '# Hello\n\n<MyComponent tag="strong">More Content...</MyComponent>';
var reactElement = converter.convert(markdown);

Available props / converter options

  • components: (object or array) Mapping of component name (tag name) to component React class (instance of createClass).

    Object form:

    var converter = new ReactShowdown.Converter({
    	components: {
    		'MyComponent': MyComponent
    	}
    });

    Array form:

    var converter = new ReactShowdown.Converter({
    	components: [{
    		name: 'MyComponent',
    		component: MyComponent,
    		block: true
    	}]
    });

All other converter options will be pushed forward to the showdown converter, please checkout the valid options section.

Block vs Inline

By default all custom React components are rendered inline in Showdown. For example:

const Component = (props={}) =>
  React.createElement(props.tag, props, props.children);


const Markdown = () => {
  const markdown = '<Component tag="span">Hello<Component>';
  return <Markdown markup={ markdown } components={{ Component }} />
}

renders to:

<p><span>Hello</span></p>

If your React component returns a block level element you will get an error:

const Markdown = () => {
  const markdown = '<Component tag="div">Hello<Component>';
  return <Markdown markup={ markdown } components={{ Component }} />
}
Warning: validateDOMNesting(...): <div> cannot appear as a descendant of <p>. See p > ... > Component > div.

To avoid this (or if you just don't want your component wrapped in <p> tags) you can use the array form of components and set the block option:

const Markdown = () => {
  const markdown = '<Component tag="div">Hello<Component>';
	const components = [{
		name: 'Component',
		component: Component,
		block: true
	}];
  return <Markdown markup={ markdown } components={ components } />
}

which renders to:

<div><p>Hello</p></div>

Credits

Project is based on the markdown parser Showdown and the "forgiving" htmlparser2.

Alternatives