.TH "NPM\-SEARCH" "1" "November 2023" "9.2.0"
.SH "NAME"
\fBnpm-search\fR
.SH Synopsis
<!\-\- AUTOGENERATED USAGE DESCRIPTIONS \-\->

.P
Note: This command is unaware of workspaces\.
.SH Description
.P
Search the registry for packages matching the search terms\. \fBnpm search\fP
.br
performs a linear, incremental, lexically\-ordered search through package
.br
metadata for all files in the registry\. If your terminal has color
.br
support, it will further highlight the matches in the results\.  This can
.br
be disabled with the config item \fBcolor\fP
.P
Additionally, using the \fB\-\-searchopts\fP and \fB\-\-searchexclude\fP options
.br
paired with more search terms will include and exclude further patterns\.
.br
The main difference between \fB\-\-searchopts\fP and the standard search terms
.br
is that the former does not highlight results in the output and you can
.br
use them more fine\-grained filtering\. Additionally, you can add both of
.br
these to your config to change default search filtering behavior\.
.P
Search also allows targeting of maintainers in search results, by prefixing
.br
their npm username with \fB=\fP\|\.
.P
If a term starts with \fB/\fP, then it's interpreted as a regular expression
.br
and supports standard JavaScript RegExp syntax\. In this case search will
.br
ignore a trailing \fB/\fP\|\.  (Note you must escape or quote many regular
.br
expression characters in most shells\.)
.SH Configuration
<!\-\- AUTOGENERATED CONFIG DESCRIPTIONS \-\->

.SH See Also

.RS 1
.IP \(bu 2
npm registry
.IP \(bu 2
npm config
.IP \(bu 2
npmrc
.IP \(bu 2
npm view
.IP \(bu 2
npm cache
.IP \(bu 2
https://npm.im/npm-registry-fetch

.RE