/home/techb158/.nvm/versions/node/v22.6.0/lib/node_modules/npm/man/man1
NameSizeModeActions
npm-access.140620644editdlrm
npm-adduser.119920644editdlrm
npm-audit.1173810644editdlrm
npm-bugs.133790644editdlrm
npm-cache.131320644editdlrm
npm-ci.1101810644editdlrm
npm-completion.19970644editdlrm
npm-config.146360644editdlrm
npm-dedupe.198620644editdlrm
npm-deprecate.118920644editdlrm
npm-diff.197710644editdlrm
npm-dist-tag.156360644editdlrm
npm-docs.133610644editdlrm
npm-doctor.153720644editdlrm
npm-edit.111800644editdlrm
npm-exec.1124910644editdlrm
npm-explain.129370644editdlrm
npm-explore.110890644editdlrm
npm-find-dupes.175900644editdlrm
npm-fund.140540644editdlrm
npm-help-search.18670644editdlrm
npm-help.110990644editdlrm
npm-hook.127080644editdlrm
npm-init.1111030644editdlrm
npm-install-ci-test.183200644editdlrm
npm-install-test.1111490644editdlrm
npm-install.1269640644editdlrm
npm-link.1129500644editdlrm
npm-login.123450644editdlrm
npm-logout.118870644editdlrm
npm-ls.194190644editdlrm
npm-org.123100644editdlrm
npm-outdated.163770644editdlrm
npm-owner.133630644editdlrm
npm-pack.138760644editdlrm
npm-ping.18490644editdlrm
npm-pkg.187040644editdlrm
npm-prefix.113170644editdlrm
npm-profile.134210644editdlrm
npm-prune.164570644editdlrm
npm-publish.183090644editdlrm
npm-query.176880644editdlrm
npm-rebuild.156640644editdlrm
npm-repo.131430644editdlrm
npm-restart.117090644editdlrm
npm-root.111940644editdlrm
npm-run-script.183770644editdlrm
npm-sbom.189960644editdlrm
npm-search.139520644editdlrm
npm-shrinkwrap.110040644editdlrm
npm-star.118070644editdlrm
npm-stars.17950644editdlrm
npm-start.118350644editdlrm
npm-stop.114660644editdlrm
npm-team.145030644editdlrm
npm-test.113790644editdlrm
npm-token.131860644editdlrm
npm-uninstall.149860644editdlrm
npm-unpublish.149000644editdlrm
npm-unstar.116580644editdlrm
npm-update.1132230644editdlrm
npm-version.177550644editdlrm
npm-view.161460644editdlrm
npm-whoami.18730644editdlrm
npm.159470644editdlrm
npx.164070644editdlrm
Edit: /home/techb158/.nvm/versions/node/v22.6.0/lib/node_modules/npm/man/man1/npm-search.1 (3952B)
.TH "NPM-SEARCH" "1" "July 2024" "NPM@10.8.2" "" .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