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

@embers-pw/markdown

v0.0.1

Published

A custom, incomplete, untested and extensible markdown parser

Downloads

3

Readme

Markdown

A custom, incomplete, untested and extensible markdown parser

Installation

With npm:

npm install @embers-pw/markdown

With yarn:

yarn add @embers-pw/markdown

Usage

import {format} from "@embers-pw/markdown";

console.log("# Hello, *world!*");
// "<h1>Hello, <em>world!</em></h1>"

How it works

Markdown consists of a tokenizer and a parser for both block and inline rules.

Tokenzers scan the input text, if they find a pattern matching a token definition, they convert it into a Token. The result of a tokenizer run is an array of Tokens for the parser to consume. If there isn't a definition, it will default to a text token.

Parsers receive the Token stream and produce a tree of Nodes resembling an Ast based on the provided rules. If the rule is recursive, the parser will run recursively on the Node contents. If no rule matches, it will default to a text node.

Finally, the renderer will take an Ast and run a renderer function for each Node. The renderer functions receive a next function that can be use to recursively render the Node.

When running format the tokenizers and parsers are ran in the order:

  • Block Tokenizer
  • Block Parser
    • Inline tokenizer?*
    • Inline parser?*
  • Renderer

* Inline tokenizer and parser are ran if the block is recursive.