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

htmlmark

v0.2.3

Published

Lightweight markdown parser

Readme

🔑 Why HtmlMark?

  • no use of external dependencies
  • lexer: to produce markdown tokens
  • parser: to produce the HTML code from the lexer
  • code highlighting support
  • support for front matter

🌐 Demo

Checkout the features of the parser from this Live Demo.

🎠 Installation

npm i htmlmark

💠 Usage

import HtmlMark from 'htmlmark';

const opts = {
	indent: 4,
	highlightFn: (code, lang) => {
		// return the highlighted code
	},
	useLinkRefs: true
};

const htmlmark = new HtmlMark(opts);

htmlmark.tokenize("## Hello World"); // returns the tokens
htmlmark.parse("## Hello World"); // returns the HTML code

🎡 Options

| Option | Type | Default | Description | |-------------|------------|-------------|---------------------------------------------------| | indent | number | 4 | Number of spaces (or tabs) to use for indentation | | tabSize | number | 4 | Equivalent spaces for a single tab used | | highlightFn | function | undefined | Function to highlight the code | | useLinkRefs | boolean | true | Whether to use link references or not |

🎢 APIs

  • tokenize(markdown: string): Token[]: Returns the lexer from the markdown string
  • parse(markdown: string): string: Returns the HTML code from the markdown string
  • getFrontMatter(markdown: string): FrontMatter{}: Returns the front matter from the markdown string

Lexer

The provided markdown string is scanned line by line and checked against various regex patterns to produce the accurate markdown tokens. A general token structure is as:

{
	"indent": 0,
	"level": 1,
	"raw": "# Heading One Text",
	"setext": false,
	"type": "heading",
	"value": "Heading One Text",
	"tokens": [{
		"raw": "Heading One Text",
		"type": "text",
		"value": "Heading One Text"
	}]
}

Front Matter

The front matter is the metadata of the markdown file. It is written in the YAML format and is separated from the markdown content by a line containing three hyphens ---. It must be placed at the top of the markdown file.

Example:

---
title: Hello World
date: 2021-01-01
author: John Doe
---

## Hello World
Lorem ipsum dollar sit amet

The above markdown file will produce the following front matter:

{
	"title": "Hello World",
	"date": "2021-01-01",
	"author": "John Doe"
}

💁 Contributing to HtmlMark

Contributions are always welcome, no matter how large or small. Before contributing, please read the code of conduct. You can also find the development guide here.

📝 License

GNU GENERAL PUBLIC LICENSE v3.0 © Kiran Parajuli