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

fenceparser

v2.2.0

Published

A well-tested parser for parsing metadata out of fenced code blocks in Markdown

Downloads

14,093

Readme

Overview ・

Assuming you have this code fence in your Markdown,

 ```ts twoslash {1-3, 5} title="Hello, World"

Using remark will yield two information about that code block, lang and meta like this.

{
  "lang": "ts",
  "meta": "twoslash {1-3, 5} title=\"Hello, World\""
}

Use fenceparser to parse the meta string out to a useful object.

import parse from 'fenceparser'

console.log(parse(meta))

// {
//   twoslash: true,
//   highlight: { '1-3': true, '5': true },
//   title: 'Hello, World'
// }

The parser won't intentionally handle parsing the language part since it is usually handled by the Markdown parsers.

But if you want to allow loose syntax grammars such as ts{1-3, 5} as well as ts {1-3, 5} which is used by gatsby-remark-vscode as an example, remark won't parse the language correctly.

{
  "lang": "ts{1-3,", // because remark uses space to split
  "meta": "5}"
}

In these cases, you can use the the library's lex function to get a properly tokenized array. You may then take out the first element as lang. For example,

import {lex, parse} from 'fenceparser'
// Notice this ^ parse is not the same the default export function

const full = [node.lang, node.meta].join(' ') // Join them back

const tokens = lex(full)
const lang = tokens.shift() // ts
const meta = parse(tokens) // { highlight: {'1-3': true, '5': true} }

Syntax

The syntax grammar is loosely based on techniques used by various syntax-highlighters. Rules are such that

  • Valid HTML attributes can be used, attribute, data-attribute, etc.
  • Just like in HTML, top-level attribute names are case insensitive.
  • Attributes without values are assigned as true
  • Attribute values can be single or double quoted strings, int/float numbers, booleans, objects or arrays
  • Non-quoted strings are valid as long as they are not separated by a whitespace or a line-break, attr=--theme-color
  • Objects can accept valid attributes as children, or valid attributes with value assigned by : keyword, {1-3, 5, ids: {7}}
  • Arrays are just like JavaScript's arrays
  • Objects without attribute keys {1-3} {7} are merged and assigned to the highlight object
  • No trailing commas

Acknowledgements

  1. This project is made initially to use with Twoslash.
  2. The initial implementations of lexer and parser are based on the examples from the book Crafting Interpreters.