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

@recital/stage-parser-cli

v0.2.0

Published

CLI for the stage parser to convert .stage files to .mdx ones

Downloads

2

Readme

stage-parser-cli

CLI for the recital stage parser to convert .stage files to .mdx ones

Usage

$ stage-parser-cli <infile> -o <outfile, optional> -t <template file, optional>

If no outfile is provided, the generated MDX will be output as a sibling file to the original. Do note that the file will not be a valid MDX file - it only converts the tags, and doesn't add proper Recital imports, etc. The generated MDX can be inserted into a Recital component via the MDXsource prop, which can cause your stories to be built faster.

Templating

You can use the -t flag to link an MDX file as a template for the output. The template should have the following format:


// put your imports at the beginning of the file

...

<Recital ...recitalProps >${content}</Recital>

...

where the generated output will all be created in the ${content} tag. Note that other tags will be ignored, and you should not have more than one content tag.

This is primarily used for stage-parser-cli to generate an entire MDX file that can be dropped into an MDX-supporting application, rather than just generating the MDX for the stage file's contents to put into a Recital component.