npms-analyzer: Should not put exact matches first

Why not allow the selection of how you want results handed to you? Kind of weird to not be able to order-by any of the metrics.

• Best match gives you the most lexically similar package
• Best Score weights the modules by their score
• Popular weights the modules by their popularity
  etc.

I think it’s funny we’re debating which should be shown when obviously it’s a subjective matter and can even change from search to search. Literally everything else on the web has a way to order by something.

Read #48 for more information.

Looks like those are just cases of the metric analysis being off, not for artificially placing exact matches at the top. I agree mithril should be before any mithril plugins, but that should be fixed in the analyzer. Doing it this way is just covering up holes in the metric analysis.

finding a specific module, that’s really bad, would be near impossible.

So your argument is not being able to find a really bad module. 😲

I use npms as a easy way to find the documentation I’m using and so when I write a name I want that exact package.

You go to npms.io, write package name, press enter, click package name, instead of just: $ npm docs package-name. I think you should revisit whether your personal use-case is worth making the search results bad.

@sindresorhus given that autosuggest and the package’s page don’t yet exist, finding a specific module, that’s really bad, would be near impossible.

As I see it, npms isn’t just about discovering. I use npms as a easy way to find the documentation I’m using and so when I write a name I want that exact package.

Nonetheless, I agree that in that case and others, it may lead to some misguidance. Maybe we could distinguish the bad package to indicate that it just shows up because of the exact name match.