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

md-to-react

v0.2.1

Published

Webpack loader for parsing Markdown into React elements

Downloads

7

Readme

md-to-react

Webpack loader for parsing Markdown into React elements.
This package requires a project with a configured Webpack build.

$ npm i md-to-react -S

markdown.md

---
description: optional yaml metadata
---
# Header

A paragraph about what's been discussed in this post.
Followed by a custom component.

<customComponent number='{22}' text='words' JSON='{{"key": "value"}}'/>

Example.js

import React from 'react'
# import some custom components to be used on the parsed markdown
import {P, CustomComponent} from './custom'

# use the webpack loader to parse the markdown file
import file from 'md-to-react!./markdown.md'

# the component hash will have its first letter lowered when rendered
const componentHash = {P, CustomComponent}

export default class Example extends React.Component {
  render() {
    return <div>
      # the meta-data will be available on the
      # object returned from the loader
      <h6>{file.description}</h6>
      # the render function will create the react elements
      # using the components it received,
      # when a component isn't found on the hash
      # a tag with its name is rendered
      # the returned elements are wrapped on a <div/>
      {file.render(componentHash)}
    </div>
  }
}

One limitation of the parser is that the html tags need to have the first letter lowercased, the render function will lowercase the first letters of the componentHash keys before executing.

This package uses js-yaml for parsing the optional yaml header, Commonmark for parsing the markdown text and Babel for transforming the html into react element calls. All the heavy lifting is done on the build phase, the render call on the front-end applies the custom components to the code generated previously.

This page was rendered using md-to-react and the components from the Stijl lib.