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

flavormark

v1.1.3

Published

TypeScript Markdown parser

Downloads

1,551

Readme

flavormark

Based on commonmark.js

FlavorMark is a Markdown parser, made in TypeScript, with emphasis placed on modularizing element parsing logic, making it easy(-ish) to add/remove syntax for your favorite Markdown flavors.

Parsers

There are a lot of classes with the word Parser in them.

  • Parser

    The main parser, parses block elements. Then, parses inline content.

  • BlockParser

    Each block element will generally be parsed by one BlockParser.

  • InlineContentParser

    Parses inline content, using InlineParser.

  • InlineParser

    Each inline element will generally be parsed by one InlineParser.

  • DelimitedInlineParser

    This parser makes it easier to parse inline elements that behave like emphasis elements.

  • DelimitedInlineSubParser

    If using DelimitedInlineParser, each sub-parser will parse one emphasis-like element. (Emphasis, smart quotes, superscript, strikethrough, etc.)

Usage

  1. Instantiate all BlockParser classes and add them to a BlockParserCollection.
  2. Instantiate all InlineParser classes and add them to an array.
  3. Instantiate an InlineContentParser and pass it the array of InlineParser.
  4. Instantiate a Parser and pass it the BlockParserCollection, and InlineContentParser.
  5. Call Parser.parse(str).

See the tests in src/test for more examples.

Notes

Each Node constructor is used to uniquely identify BlockParser, and HtmlSubRenderer instances.

When trying to parse a block, instanceof checks are used to find the BlockParser associated with a Node. The first matching BlockParser in the array is used.

For this reason, each unique block type should have its own Node sub-class.

License

See LICENSE file (copy-pasted from commonmark.js). Also, since this is just a glorified port of commonmark.js, I guess the BSD-license carries over. I have no idea how this works. I don't really care, personally. I just don't want to step on anyone's toes.