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

@kenthackenough/mdx

v1.0.36

Published

Utilizes [mdx.js](https://mdxjs.com/)

Downloads

2

Readme

Markdown Renderer

Utilizes mdx.js

Render to HTML

import { Button } from '@mantine/core';
import { ReactMarkdownRenderer } from '@kenthackenough/mdx/render';
import * as runtime from 'react/jsx-runtime';

const mdx = new ReactMarkdownRenderer({
    runtime, // JSX Runtime
    styles: [
        `.red { color: red }`,
        `.blue { color: blue }`,
    ],
    components: {
        Button,
    }
})

const output: string = await mdx.render(`

# Hi there!

<span class="blue">yeyeye!</span>

<Button class="red">click me!</Button>

`);

This outputs the following HTML into the output varaible above.

<html>

<head></head>

<body>
    <h1>Hi there!</h1>
    <span style="color:blue">yeyeye!</span>
    <button type="button" data-button="true" style="color:red">
        <div><span>click me!</span></div>
    </button>
</body>

</html>

Compile to a React Element

import { Button } from '@mantine/core';
import { ReactMarkdownCompiler } from '@kenthackenough/mdx/compile';
import * as runtime from 'react/jsx-runtime';

const mdx = new ReactMarkdownCompiler({
    runtime, // JSX Runtime
    components: {
        Button,
    }
})

const output: JSX.Element = await mdx.compile(`

# Hi there!

<Button>click me!</Button>

`);

function SomeComponent() {
    return <div>
        {output}
    </div>
}

Note

ReactMarkdownRenderer inherits from ReactMarkdownCompiler, including additional helper functions to apply styles and properly serialize the react component into static markup.

Although ReactMarkdownRenderer can do everything ReactMarkdownCompiler can, it relies on additional libraries. It is not recommended to use the Renderer if you have access to React rendering elsewhere in the application.

  • For example, the Compiler should be used in Next.js because you can have Next.js render the component for you, so you need not import the necessary libraries to render React.