repro:
go to npm, right-click. Wait for new package installer to load up.
in the search box type require-directory
result:
hundreds or results back.
require-directory *is* in the list but it's a long way down.
thoughts:
This is a particularly bad example as the word "require" is so common but it looks like it's not treating the input string as a single keyword and it's returning results even if only the first part of the keyword matches any part of a package description.
desired result.
if there's an exact match to the package name, promote this result to the top and tell the user something like "exact match found"
optional
- add a "see more results" option to show the remainder.
- enable search options to limit to package names only or similar.
Comments: update: I'm able to find it as a single result if I type the package name *and* author name into the search box but that's a workaround :)
go to npm, right-click. Wait for new package installer to load up.
in the search box type require-directory
result:
hundreds or results back.
require-directory *is* in the list but it's a long way down.
thoughts:
This is a particularly bad example as the word "require" is so common but it looks like it's not treating the input string as a single keyword and it's returning results even if only the first part of the keyword matches any part of a package description.
desired result.
if there's an exact match to the package name, promote this result to the top and tell the user something like "exact match found"
optional
- add a "see more results" option to show the remainder.
- enable search options to limit to package names only or similar.
Comments: update: I'm able to find it as a single result if I type the package name *and* author name into the search box but that's a workaround :)