npm Community Forum (Archive)

The npm community forum has been discontinued.

To discuss usage of npm, visit the GitHub Support Community.

No search results on npmjs.com

Search function recently stopped working on npmjs.com

What I Wanted to Do

Search results are supposed to be available when navigating to search results page, https://www.npmjs.com/search?q=npm

What Happened Instead

Search results page shows 0 packages found, despite that search results are available in search field’s autocomplete. Search results are also available on npms.io, which npmjs.com seems to use.

Reproduction Steps

Use search field to search for a package, like https://www.npmjs.com/search?q=npm


Many queries work, but I’m getting the same absence of results for ‘graphql-tag‘: https://www.npmjs.com/search?q=graphql-tag
Autocomplete popup yes, search page no.


Same thing here.

https://www.npmjs.com/search?q=xml

Autocomplete has results but that page has zero


There are no results returned for http://registry.npmjs.org/-/v1/search?text=kinvey-nativescript-sdk but the package is present (not deprecated) at https://www.npmjs.com/package/kinvey-nativescript-sdk


https://www.npmjs.com/search?q=ts-node -> https://www.npmjs.com/package/ts-node


Same thing for accessing https://www.npmjs.com/search?q=bic
But bic exists: https://www.npmjs.com/package/bic


Also seeing this with the query “base64”: https://www.npmjs.com/search?q=base64

The command line search, npm search base64, also shows returns No matches found for "base64".

The results for the query do show, however, in the autocompletion dropdown.

The queries “zlib” and “gzip”, for example, do not have this issue.


There is an open issue on https://status.npmjs.org/. You could subscribe for updated from here.


Latest updates states:

Update - We are continuing to work on a fix for this issue. Three character package names are currently not being returned in search results.

However, all of the longer-than-three-character-names examples in this thread are still not returned in the search results.


It seems the problem is not just about the length of characters, but that any search that contains digits will not return any result, for both the npm search CLI and the website. For example, “npm search utf8”, “npm search base64”, “npm search web3”, “npm search node-fetch-http2”, “npm search through2” all returns “No matches found”, while “npm search node-fetch-http” and “npm search through” work perfectly.


this made me giggle abit

~$ npm search npm
No matches found for "npm"
   ╭───────────────────────────────────────────────────────────────╮
   │                                                               │
   │       New minor version of npm available! 6.7.0 → 6.9.0       │
   │   Changelog: https://github.com/npm/cli/releases/tag/v6.9.0   │
   │               Run npm install -g npm to update!               │
   │                                                               │
   ╰───────────────────────────────────────────────────────────────╯


A search for node-red does not return results and a search for node-red-contrib either or a search for pid for that matter. Not on the commandline or on the website. This seems to be a recurring issue. It has happened before, then it worked for a while and it is back again. What gives?


It works again now. This is so strange.