The most popular markdown parser on npm hasn't seen a release in 7 years, and the second most popular markdown parser emits an unclosed <em> whenever you use *emphasis* syntax on any line other than the last line of a paragraph.
Show this thread
-
Does anyone except me care about any of this? It feels like everyone else is content to have everything break at random on a daily basis, then often stay broken for months or sometimes forever. (This is an actual question; I don't mean it dismissively.)
Show this thread
I don't know how NPM rates "popularity", but as one of the maintainers of a package registry I can guarantee it is almost certainly worse than what you'd get if you Google "node + think you are trying to do" (and that may have the same result in which case ¯\_(ツ)_/¯)
-
-
Gave that a try and got the abandoned-for-7-years package followed by some other packages that have fewer weekly downloads than the one that's broken.
-
That may just be what folks are using though. Abandoned for 7 years means it's for sure something other than commonmark, but maybe that's fine?
- 5 more replies
New conversation -
-
-
Answering "what package are people using to solve this problem" isn't a thing that we can easily answer without a lot more tracking than any registry is doing AFAIK
-
Oh I was just going for number of downloads. In NPM, search for "markdown", sort matching packages by popularity, and the first result has 58k weekly downloads followed by the second result with over 3 million. So it just seems wrong?
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.