website keyword search broken for keywords with spaces

website

(Jordan Harband) #1

What I Wanted to Do

Click https://www.npmjs.com/browse/keyword/es-shim%20API (search for the keyword “es-shim API”) and get a list of all packages that have it, like I used to be able to (so https://github.com/es-shims/es-shim-api/blob/master/shims.md can dynamically link to all packages using the keyword)

What Happened Instead

0 packages found.

Reproduction Steps

https://www.npmjs.com/browse/keyword/es-shim%20API

Details

Since I can publish packages with keywords that have spaces, and since npmjs.com used to allow searching for them, I expect to be able to do so now.

Platform Info

n/a


npmjs.org package pages are missing percent-encoding for keyword hyperlinks
(Kat Marchán) #2

This is a duplicate of npmjs search is completely broken and does not find many packages and others. Keep an eye on the incident report to find out as soon as it get fixed. You can use npms.io in the meantime. :slight_smile:


(Jordan Harband) #3

Thanks, and my mistake - I assumed it was a specific regression as opposed to a wider outage.


(Kat Marchán) #4

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


(Jordan Harband) #5

This particular search (with a space) seems to still be broken - it returns 0 results (it should return 29, per https://npms.io/search?q=es-shim+API)


(Kat Marchán) #6

Oh. You have to use ". Which is reasonable enough. The rest is updating the website so links to keyword searches with spaces get "-wrapped


(Jordan Harband) #7

Gotcha, I can use that as a workaround, although that’s still an unfortunate regression, since it used to work.


(Jordan Harband) #8

Actually the original link I have is https://www.npmjs.com/browse/keyword/es-shim%20API - which seems to redirect without the quotes wrapping.

Is that something that could be fixed on npm’s side? That way the quotes would only be needed in the query string version.


(system) #9

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