npmjs search is completely broken and does not find many packages

website
registry

(Wiktor Walc) #1

The search engine is seriously broken. Lots of packages are not listed at all and people are pointed to random packages without any reasonable algorithm.

What I Wanted to Do

I tried to find ckeditor packages using “ckeditor” as a search phrase.

What Happened Instead

The most important packages are not found at all.

Reproduction Steps

The 2 links limit protects me from typing more links :(
For working links open https://gist.github.com/wwalc/579cc75725042002fdeccb867bf7bdcb

npmjs com search?q=ckeditor
returns just 13 results, while over 60 packages should be returned.

The most important packages are not returned at all:

package/ckeditor (~18000 weekly downloads)
package/@ckeditor/ckeditor5-build-classic (~5000 weekly downloads)
package/@ckeditor/ckeditor5-build-balloon (~8000 weekly downloads)

but, strangely one of the forks is returned.

The CKEditor organisation has 60 packages published on npm (mostly CKEditor 5-related), including packages such as mentioned above:

package/@ckeditor/ckeditor5-build-classic (~5000 weekly downloads)
package/@ckeditor/ckeditor5-build-balloon (~8000 weekly downloads)

Under the CKSource account we also have different packages, including this with CKEditor 4

package/ckeditor (~18000 weekly downloads)

Details

The website claims that it is using npms.io for searching.
“powered by npms io :rocket:

But npms io returns correctly 220 results and in much better order.
So is the website really using npms io?

Platform Info

Search made on Google Chrome, if that makes any difference.


The search on the NPM doesn't match the keyword with exact package name but shows other results first.
https://www.npmjs.com can't search @babel/preset-env
search doesn't return exact match
website keyword search broken for keywords with spaces
(Jason) #2

I have the same issue with @babel/preset-env I just use https://npms.io/ or https://yarnpkg.com/ instead, those two are working perfectly


(Kat Marchán) #3

There is an ongoing incident having to do with search. Please subscribe to the incident report for updates.


(Nick O'leary) #4

Would it be possible to get an update on that incident report? I raised the original github issue 15 days ago and the incident was last updated 12 days ago. I appreciate there’s lots going on, and I’m very grateful for the work done here to keep things ticking.

We noticed the search results for the ‘node-red’ keyword (which previously had ~1800 results) dropped to 0 results yesterday and has since climbed back to 99. From that I infer you’re rebuilding the search index from scratch - but it would be great to know that for sure. We have a bunch of automation that uses those search results to detect when new node-red nodes are published or updated - which I’ve had to turn off for the time being.


(Kat Marchán) #5

@knolleary you can subscribe to incident reports and get updates as soon as they’re available. If the report is not updated, that means we have nothing new to share about its resolution.

We would’ve fixed this sooner, but we were a bit distracted last week, and generating search indices takes hella time.


(Nick O'leary) #6

@zkat Thanks for updating the incident report. I am subscribed and it was the lack of update when I could see ‘things’ happening that prompted my question to confirm what was going on.

Thanks!


(Kat Marchán) #7

The incident has been resolved, so this works again. Cheers!


(system) #8

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.