Discussion on this started here. We'd really like to be able to npm|bower install stmd. What's the roadmap for that? Is it close to production ready?

My impression - by looking at the code (and having written quite a few JS tokenizers / parsers in the past) - is that the current parser seems to be heavily regex based, so it's going to be "relatively" slow. For real production code, there's definitely the need for a optimized parser which does not use regular expressions and would be heavily optimized with use of the v8 tools to get rid of the JIT bottlenecks / GC pauses.

This is no small task though and would take at least a week or two of full time work. I would definitely welcome such a version on npm / bower, the current markdown modules out there all have their issues and having a really fast de facto standard version on NPM would help a lot to making it the actual standard

If I find the time, I'll start work on a fast version this weekend.

+++ kentcdodds [Sep 03 14 20:41 ]:

Discussion on this started [2]here. We'd really like to be able to npm|bower install stmd. What's the roadmap for that? Is it close to production ready?

It is well tested, but I'd like to have some javascript experts look at the code. It's also possible that the API should be different; again, I'd welcome feedback here.

In due time I would definitely be in favor of putting it on npm. But today is probably too early!