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 🙏

© 2026 – Pkg Stats / Ryan Hefner

typesite-jsx-renderer

v1.2.0

Published

Typesite plugin to render JSX to HTML

Readme

Typesite-filter-out

A plugin for Typesite that allows you to render JSX to HTML easily, even if you want to have multiple JSX fragments in the same file.

Installation

Run npm install typesite-filter-out

How to use

First register JsxRendererPlugin plugin in your Typesite project:

typesite.use(new JsxRendererPlugin(true));

Then add JsxContentsMeta to the frontmatter of whatever files you want to have JSX contents. It takes a callback which will be given ContentFile and Typesite as params and will expect you to return JSX.Element.

This will overwrite content sent by just having a string in the frontmatter.

export default new Frontmatter(
    new JsxContentsMeta((path:string, file:ContentFile, files:ContentFileCollection, typesite:Typesite) => {
        return <div className="main-page">
            This will be my <strong>main</strong> content
        </div>;
    }),
    "This string content will be overwritten."
);

Multiple JSX fragments

If you want to have multiple JSX fragments in one file, for example a summary for a blog post, you first have to create a new class extending JsxContentsMeta:

export class JsxSummaryMeta extends JsxContentsMeta{
    getKey(): string {
        return "summaryJsx";
    }
}

It's absolutely necessary to override getKey! Then register the meta in frontmatter:


export default new Frontmatter(
    new JsxContentsMeta((path:string, file:ContentFile, files:ContentFileCollection, typesite:Typesite) => ...),
    new JsxSummaryMeta((path:string, file:ContentFile, files:ContentFileCollection, typesite:Typesite) => ...)
);

You can later access its contents as string with:

file.metadata.getItem(JsxSummaryMeta).contents;

Important: when you have multiple metas extending JsxContentsMeta only the base one will be transferred to ContentFile's contents.

API

JsxContentsPlugin

The plugin responsible for rendering the JSX metas:

constructor

  • Argument removeDataReactRoot :boolean Controls wheteher to remove any and all data-reactroot attributes that might appear

JsxContentsMeta

Meta class that builds the JSX for the page's contents:

constructor

  • Argument render: (path:string, file:ContentFile, files:ContentFileCollection, typesite:Typesite) => JSX.Element A function that expects file path, rendered file, files collection & typescite instace and should return JSX.Element with the page's contents which will later be rendered to string.
  • Exception Typesite.ArgumentNullError When render is null
  • Exception Typesite.ArgumentInvalidError When render is not a function

Properties

  • contents:string The rendered JSX