/opt/cpanel/ea-nodejs22/lib/node_modules/npm/man/man1/
/opt/cpanel/ea-nodejs22/lib/node_modules/npm/man/man1
NameSizeModeActions
npm-access.140630644editdlrm
npm-adduser.119930644editdlrm
npm-audit.1173820644editdlrm
npm-bugs.133800644editdlrm
npm-cache.131330644editdlrm
npm-ci.1101820644editdlrm
npm-completion.19980644editdlrm
npm-config.146370644editdlrm
npm-dedupe.198630644editdlrm
npm-deprecate.118930644editdlrm
npm-diff.197720644editdlrm
npm-dist-tag.156370644editdlrm
npm-docs.133620644editdlrm
npm-doctor.153730644editdlrm
npm-edit.111810644editdlrm
npm-exec.1124920644editdlrm
npm-explain.129380644editdlrm
npm-explore.110900644editdlrm
npm-find-dupes.175910644editdlrm
npm-fund.140550644editdlrm
npm-help-search.18680644editdlrm
npm-help.111000644editdlrm
npm-hook.127090644editdlrm
npm-init.1111110644editdlrm
npm-install-ci-test.183210644editdlrm
npm-install-test.1111500644editdlrm
npm-install.1267720644editdlrm
npm-link.1129510644editdlrm
npm-login.123460644editdlrm
npm-logout.118880644editdlrm
npm-ls.194200644editdlrm
npm-org.123110644editdlrm
npm-outdated.163780644editdlrm
npm-owner.133640644editdlrm
npm-pack.138770644editdlrm
npm-ping.18500644editdlrm
npm-pkg.187050644editdlrm
npm-prefix.113180644editdlrm
npm-profile.134220644editdlrm
npm-prune.164580644editdlrm
npm-publish.183100644editdlrm
npm-query.176890644editdlrm
npm-rebuild.156650644editdlrm
npm-repo.131440644editdlrm
npm-restart.117100644editdlrm
npm-root.111950644editdlrm
npm-run-script.183780644editdlrm
npm-sbom.189970644editdlrm
npm-search.139530644editdlrm
npm-shrinkwrap.110050644editdlrm
npm-star.118080644editdlrm
npm-stars.17960644editdlrm
npm-start.118360644editdlrm
npm-stop.114670644editdlrm
npm-team.145040644editdlrm
npm-test.113800644editdlrm
npm-token.131870644editdlrm
npm-uninstall.149870644editdlrm
npm-unpublish.149010644editdlrm
npm-unstar.116590644editdlrm
npm-update.1132240644editdlrm
npm-version.177560644editdlrm
npm-view.161470644editdlrm
npm-whoami.18740644editdlrm
npm.159480644editdlrm
npx.164080644editdlrm
Edit: /opt/cpanel/ea-nodejs22/lib/node_modules/npm/man/man1/npm-search.1 (3953B)
.TH "NPM-SEARCH" "1" "March 2026" "NPM@10.9.8" "" .SH "NAME" \fBnpm-search\fR - Search for packages .SS "Synopsis" .P .RS 2 .nf npm search \[lB] ...\[rB] aliases: find, s, se .fi .RE .P Note: This command is unaware of workspaces. .SS "Description" .P Search the registry for packages matching the search terms. \fBnpm search\fR performs a linear, incremental, lexically-ordered search through package metadata for all files in the registry. If your terminal has color support, it will further highlight the matches in the results. This can be disabled with the config item \fBcolor\fR .P Additionally, using the \fB--searchopts\fR and \fB--searchexclude\fR options paired with more search terms will include and exclude further patterns. The main difference between \fB--searchopts\fR and the standard search terms is that the former does not highlight results in the output and you can use them more fine-grained filtering. Additionally, you can add both of these to your config to change default search filtering behavior. .P Search also allows targeting of maintainers in search results, by prefixing their npm username with \fB=\fR. .P If a term starts with \fB/\fR, then it's interpreted as a regular expression and supports standard JavaScript RegExp syntax. In this case search will ignore a trailing \fB/\fR . (Note you must escape or quote many regular expression characters in most shells.) .SS "Configuration" .SS "\fBjson\fR" .RS 0 .IP \(bu 4 Default: false .IP \(bu 4 Type: Boolean .RE 0 .P Whether or not to output JSON data, rather than the normal output. .RS 0 .IP \(bu 4 In \fBnpm pkg set\fR it enables parsing set values with JSON.parse() before saving them to your \fBpackage.json\fR. .RE 0 .P Not supported by all npm commands. .SS "\fBcolor\fR" .RS 0 .IP \(bu 4 Default: true unless the NO_COLOR environ is set to something other than '0' .IP \(bu 4 Type: "always" or Boolean .RE 0 .P If false, never shows colors. If \fB"always"\fR then always shows colors. If true, then only prints color codes for tty file descriptors. .SS "\fBparseable\fR" .RS 0 .IP \(bu 4 Default: false .IP \(bu 4 Type: Boolean .RE 0 .P Output parseable results from commands that write to standard output. For \fBnpm search\fR, this will be tab-separated table format. .SS "\fBdescription\fR" .RS 0 .IP \(bu 4 Default: true .IP \(bu 4 Type: Boolean .RE 0 .P Show the description in \fBnpm search\fR .SS "\fBsearchlimit\fR" .RS 0 .IP \(bu 4 Default: 20 .IP \(bu 4 Type: Number .RE 0 .P Number of items to limit search results to. Will not apply at all to legacy searches. .SS "\fBsearchopts\fR" .RS 0 .IP \(bu 4 Default: "" .IP \(bu 4 Type: String .RE 0 .P Space-separated options that are always passed to search. .SS "\fBsearchexclude\fR" .RS 0 .IP \(bu 4 Default: "" .IP \(bu 4 Type: String .RE 0 .P Space-separated options that limit the results from search. .SS "\fBregistry\fR" .RS 0 .IP \(bu 4 Default: "https://registry.npmjs.org/" .IP \(bu 4 Type: URL .RE 0 .P The base URL of the npm registry. .SS "\fBprefer-online\fR" .RS 0 .IP \(bu 4 Default: false .IP \(bu 4 Type: Boolean .RE 0 .P If true, staleness checks for cached data will be forced, making the CLI look for updates immediately even for fresh package data. .SS "\fBprefer-offline\fR" .RS 0 .IP \(bu 4 Default: false .IP \(bu 4 Type: Boolean .RE 0 .P If true, staleness checks for cached data will be bypassed, but missing data will be requested from the server. To force full offline mode, use \fB--offline\fR. .SS "\fBoffline\fR" .RS 0 .IP \(bu 4 Default: false .IP \(bu 4 Type: Boolean .RE 0 .P Force offline mode: no network requests will be done during install. To allow the CLI to fill in missing cache data, see \fB--prefer-offline\fR. .SS "See Also" .RS 0 .IP \(bu 4 npm help registry .IP \(bu 4 npm help config .IP \(bu 4 npm help npmrc .IP \(bu 4 npm help view .IP \(bu 4 npm help cache .IP \(bu 4 https://npm.im/npm-registry-fetch .RE 0