Popular posts

Gijo Varghese

A WordPress speed enthusiast

Sep 7, 2018

Looks like a really good idea. I've faced this problem before. I've even posted a question in Hasnode itself do decide a framework ( Loopback vs FeathersJS )

It's the same points I looked before deciding. However, one more I noticed is the issue open to close timing, no. of questions in StackOverflow, backlinks to that repo or their official docs. If you can include those it would be great.

However, I was confused on what to search on your site, SearchLibs. For example, Loopback and Feathers are the top rest API framework in NodeJS. It tried searching "rest node", "rest framework js", no results contain Loopback or Feathers, not even ExpressJS!!

I tried searching some libraries with exact names, like Cheerio a popular framework for parsing HTML in node js. The result I got is: github.com/DefinitelyTyped/DefinitelyTyped it doesn't even contain a word Cheerio and it was flagged as old. Does old have a low ranking? I think the search algorithm needs some changes

Kamil Tomšík

Sep 7, 2018

Thanks for your feedback, really.

You're right it still has some issues but latest release of cheerio was more than year ago. It's obviously not a dead project but it's not very active either - healthy projects usually have at least few releases during the year. Inactive projects are simply moved down (but before new projects).

SearchLibs doesn't do any relevance searching (it could but I think it's too much magic), you only get what you ask for, which is sometimes good (search rest api) and sometimes not (rest framework). I think if there were term suggestions it could resolve this issue but again, I'm open to anyone opinions.

You've also mentioned DefinitelyTyped - I'm actually thinking about being able to leave these results out (with UI). In the meantime you can exclude anything with -keyword syntax.

And lastly, favoring exact results sounds good (npm/yarn do it) but if you search for date you get package date, with 10 stars and latest release 7 years ago BTW: for some reason, yarn thinks this package is 1 year old but no, it's really 7 years.

Search Hashnode