XIxixixao·Dec 4, 2013Submission
Make a fork, get your PR accepted
2 points · Open discussionmarkedjs
marked
TypeScript2012–2026
markedjs / marked
marked
A markdown parser and compiler. Built for speed.
21Distinct people
26Mentions
1Explicit recommenders
37.3KGitHub stars
What to know before exploring
What it is
A markdown parser and compiler. Built for speed.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
I recommend upgrading to the latest release of marked ( https://github.com/chjj/marked/tree/v0.2.8 ). It has a few improvements as well as GFM tables.
chjj used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- markdown-it/markdown-it · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:17:07 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year26 dated mentions
Observed mentions: 2012-01-09 03:35:16 UTC to 2026-07-07 19:10:24 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 7 | 1 | 6 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 5 | 0 | 5 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
7 sourcesDone and done. https://github.com/chjj/marked/issues/277
In How to linkify Markdown headers in nodeOP should publish a patch instead of telling people to modify the code by hand, and/or submit a pull request to the repo [1].
[1]: https://github.com/chjj/marked
In How to linkify Markdown headers in nodeChrome not happy :(
Refused to execute script from 'https://github.com/chjj/marked/raw/master/lib/marked.js because its MIME type ('text/plain') is not executable, and strict MIME type checking is enabled.
FF not happy either
ReferenceError: marked is not defined
In Pretty, fast client-side markdown is really easyOh, he didn't mention half the stuff I thought he would. He's right about a lot of things though.
Take this for example:
Hello world, there isn't
1. There are 4.
The original markdown treats the second line as a continuation of a line in a single paragraph. Github treats the second line as the start of an ordered list. Why? Because then you can do things like this:
# My list
1. foo
...
I've been so torn about how to implement so many of these things. I've had a lot of people ask me about that particular issue, and when I tell them the original markdown behavior requires 2 newlines after a line before starting a list, it was the last thing they expected.
The main problem with markdown is not the fact that these counterintuitive things exist, but the fact that they're not consistently implemented. I've spent nearly 2 y
Read the rest
ears trying to reconcile all these differences. See https://github.com/chjj/marked for more crazy markdown nonsense in the test suite.
Author here, that's correct, we haven't implemented the WebRTC binding yet. The way grim's communication works, we put REST semantics and protocol over messaging transports. We've already done it over Web Workers' postMessage API, and don't expect any trouble doing the same over WebRTC's DataChannels. In fact, the blog post's content is served by a Worker server which proxies out to a markdown file on the remote host, converts to HTML using https://github.com/chjj/marked, and responds.
In Grimwire.js: A RESTful Browser OS that does Peer-to-peer over WebRTCI recommend upgrading to the latest release of marked ( https://github.com/chjj/marked/tree/v0.2.8 ). It has a few improvements as well as GFM tables.
In Show HN: Markdown + LaTeX math in the browser