Search querying
Typing quickly and pressing enter in the package search before the results appear causes navigation to a prior state of the search results.
For example, enter "rollup", which naturally brings up rollup in the search results. Then quickly add " plugin typescript" and hit enter. The page navigates to rollup (prior result) rather than the search query's new result.
Search result navigation
After searching, the result list has a fade-in effect which prevents quick scrolling and prevents the use of find-in-page.
Granted there is pagination going on, but even after reaching the end, find-in-page is still ineffective.
Search weights (same as npmjs.com)
This is a minor issue in comparison, but it seems like the words in the description equal or outweigh the words in the package name.
I've entered a query which sequentially matches to an actual package name, but it comes in third.
https://npmx.dev/search?q=typescript+eslint+plugin
Search querying
Typing quickly and pressing enter in the package search before the results appear causes navigation to a prior state of the search results.
For example, enter "rollup", which naturally brings up rollup in the search results. Then quickly add " plugin typescript" and hit enter. The page navigates to rollup (prior result) rather than the search query's new result.
Search result navigation
After searching, the result list has a fade-in effect which prevents quick scrolling and prevents the use of find-in-page.
Granted there is pagination going on, but even after reaching the end, find-in-page is still ineffective.
Search weights (same as npmjs.com)
This is a minor issue in comparison, but it seems like the words in the description equal or outweigh the words in the package name.
I've entered a query which sequentially matches to an actual package name, but it comes in third.
https://npmx.dev/search?q=typescript+eslint+plugin