Go to file
Christopher Jeffrey 2aaeaaaa8a inline
2011-08-13 21:04:18 -05:00
bin bin, again 2011-08-10 21:51:44 -05:00
lib inline 2011-08-13 21:04:18 -05:00
test test 2011-08-10 21:55:10 -05:00
index.js mode 2011-07-31 17:27:10 -05:00
LICENSE bin, tests 2011-08-10 21:50:25 -05:00
package.json bin, tests 2011-08-10 21:50:25 -05:00
README.md readme 2011-08-10 21:52:54 -05:00

marked

A full-featured markdown parser and compiler implemented in ~370 lines of JS.
Built for speed.

Benchmarks

$ node test/bench
marked: 6260ms
showdown: 21665ms
markdownjs: 69168ms

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 lingers around 350 lines long and still implements all markdown features.

Install

$ npm install marked

Usage

var marked = require('marked');
console.log(marked('i am using __markdown__.'));

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

var tokens = marked.lexer(str);
console.log(marked.parser(tokens));

Todo (& notes to self)

This parser was written in one night, so there's still a lot on the todo list. There may also be some bugs.

  • Implement GFM features.
  • Optimize the parser so it accepts a stream of tokens from the lexer. This should enhance performance even further, although, no lookaheads would be possible.
  • Write actual rules for inline markup (links, em, strong, etc). Currently, only blocks are tokenized.
  • Possibly add some ReMarkable features while remaining backwardly compatible with all markdown syntax.
  • Find a better way of testing. Create a test suite from scratch because most markdown compilers don't appear to be working properly in every aspect (but it's hard to tell because the markdown "spec" is so vague).
  • Possibly alter rules to recognize arbitrary blocks of HTML better.
  • Recognize and parse paragraph list items better.
  • Add an explicit pretty printing and minification feature.
  • Handle escaping of HTML entities better.
  • Client-side compatibility.

I've still just begun to write this. I expect I will be updating it frequently.