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

marked-component

v0.2.9

Published

A markdown parser built for speed

Readme

marked

A full-featured markdown parser and compiler, written in JavaScript. Built for speed.

NPM version

Install

npm install marked --save

Usage

Minimal usage:

console.log(marked('I am using __markdown__.'));
// Outputs: <p>I am using <i>markdown</i>.</p>

Example using all options:

// Set default options except highlight which has no default
marked.setOptions({
  gfm: true,
  highlight: function (code, lang, callback) {
    pygmentize({ lang: lang, format: 'html' }, code, function (err, result) {
      callback(err, result.toString());
    });
  },
  tables: true,
  breaks: false,
  pedantic: false,
  sanitize: true,
  smartLists: true,
  smartypants: false,
  langPrefix: 'lang-'
});

console.log(marked('I am using __markdown__.'));

marked(markdownString, [options], [callback])

markdownString

Type: String

String of markdown source to be compiled.

options

Type: Object

Hash of options. Can also be set using the marked.setOptions method as seen above.

callback

Type: Function

Function called when the markdownString has been fully parsed. If the options argument is omitted, this can be used as the second argument as follows:

marked(markdownString, function (err, content) {
  if (err) throw err;
  console.log(content);
  // Outputs parsed html
});

Options

gfm

Type: Boolean Default: true

Enable GitHub flavored markdown.

highlight

Type: Function

A function to highlight code blocks. The function takes three arguments: code, lang, and callback. The above example uses async highlighting with node-pygementize-bundled, and here is a synchronous example using highlight.js which doesn't require the callback argument:

marked.setOptions({
  highlight: function (lang, code) {
    return hljs.highlightAuto(lang, code).value;
  }
});

highlight arguments

code

Type: String

The section of code to pass to the highlighter.

lang

Type: String

The programming language specified in the code block.

callback

Type: String

The callback function to call when using an async highlighter.

tables

Type: Boolean Default: true

Enable GFM tables. This option requires the gfm option to be true.

breaks

Type: Boolean Default: false

Enable GFM line breaks. This option requires the gfm option to be true.

pedantic

Type: Boolean Default: false

Conform to obscure parts of markdown.pl as much as possible. Don't fix any of the original markdown bugs or poor behavior.

sanitize

Type: Boolean Default: true

Sanitize the output. Ignore any HTML that has been input.

smartLists

Type: Boolean Default: true

Use smarter list behavior than the original markdown. May eventually be default with the old behavior moved into pedantic.

smartypants

Type: Boolean Default: false

Use "smart" typograhic punctuation for things like quotes and dashes.

langPrefix

Type: String Default: lang-

Set the prefix for code block classes.

Access to lexer and parser

You also have direct access to the lexer and parser if you so desire.

var tokens = marked.lexer(text, options);
console.log(marked.parser(tokens));
var lexer = new marked.Lexer(options);
var tokens = lexer.lex(text);
console.log(tokens);
console.log(lexer.rules);

CLI

$ marked -o hello.html
hello world
^D
$ cat hello.html
<p>hello world</p>

Benchmarks

node v0.4.x

$ node test --bench
marked completed in 12071ms.
showdown (reuse converter) completed in 27387ms.
showdown (new converter) completed in 75617ms.
markdown-js completed in 70069ms.

node v0.6.x

$ node test --bench
marked completed in 6448ms.
marked (gfm) completed in 7357ms.
marked (pedantic) completed in 6092ms.
discount completed in 7314ms.
showdown (reuse converter) completed in 16018ms.
showdown (new converter) completed in 18234ms.
markdown-js completed in 24270ms.

Marked is now faster than Discount, which is written in C.

For those feeling skeptical: These benchmarks run the entire markdown test suite 1000 times. The test suite tests every feature. It doesn't cater to specific aspects.

node v0.8.x

$ node test --bench
marked completed in 3411ms.
marked (gfm) completed in 3727ms.
marked (pedantic) completed in 3201ms.
robotskirt completed in 808ms.
showdown (reuse converter) completed in 11954ms.
showdown (new converter) completed in 17774ms.
markdown-js completed in 17191ms.

Another Javascript Markdown Parser

The point of marked was to create a markdown compiler where it was possible to frequently parse huge chunks of markdown without having to worry about caching the compiled output somehow...or blocking for an unnecesarily long time.

marked is very concise and still implements all markdown features. It is also now fully compatible with the client-side.

marked more or less passes the official markdown test suite in its entirety. This is important because a surprising number of markdown compilers cannot pass more than a few tests. It was very difficult to get marked as compliant as it is. It could have cut corners in several areas for the sake of performance, but did not in order to be exactly what you expect in terms of a markdown rendering. In fact, this is why marked could be considered at a disadvantage in the benchmarks above.

Along with implementing every markdown feature, marked also implements GFM features.

$ node
> require('marked').lexer('> i am using marked.')
[ { type: 'blockquote_start' },
  { type: 'paragraph',
    text: 'i am using marked.' },
  { type: 'blockquote_end' },
  links: {} ]

License

Copyright (c) 2011-2013, Christopher Jeffrey. (MIT License)

See LICENSE for more info.