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
-
I'm on day two of a completely normal "update all of our dependencies" cycle and it feels like it will never end. Really making me wish I weren't married to the Node+npm ecosystem. No other ecosystem that I've worked in has been like this.
7 replies 15 retweets 98 likesShow this thread -
Apparently those popularity rankings that I quoted were wrong, because sorting by "popularity" in NPM doesn't seem to sort by popularity.
3 replies 1 retweet 59 likesShow 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.)
34 replies 2 retweets 130 likesShow this thread -
Replying to @garybernhardt
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 ¯\_(ツ)_/¯)
2 replies 0 retweets 0 likes -
Replying to @sgrif @garybernhardt
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
1 reply 0 retweets 0 likes -
Replying to @sgrif
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 reply 0 retweets 0 likes
It looks like NPM always gives the package that exactly matches your search string first (http://crates.io does the same, but I think we only do that if you sort by "relevance")
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.