You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current sorting seems a bit off.
E.g. searching "express" (by clicking on example on home page) returns "ifade" as top result. I assume because it has "Expressions" in its description.
What I'd expect/want to see when I search for "express" is express.js itself on top + all the relevant express-* modules (so, primary sort by title string matching should work here), which are then sorted by e.g. popularity + latest update.
Does this makes sense?
The text was updated successfully, but these errors were encountered:
I've been having the same experience. The results are returning queries in unpredictable order. A search query that is a part of a package name won't return the package name. Are there any additional tips on fine-tuning the search queries? npmsearch.com itself has predictable results, how can we achieve the same from the CURL API?
Current sorting seems a bit off.
E.g. searching "express" (by clicking on example on home page) returns "ifade" as top result. I assume because it has "Expressions" in its description.
What I'd expect/want to see when I search for "express" is express.js itself on top + all the relevant express-* modules (so, primary sort by title string matching should work here), which are then sorted by e.g. popularity + latest update.
Does this makes sense?
The text was updated successfully, but these errors were encountered: