Man page - npm-fund(1)
Packages contas this manual
- npm-explain(1)
- npm-star(1)
- npm-logout(1)
- npm-arborist(1)
- package-lock-json(5)
- npm-bugs(1)
- npm-shrinkwrap(1)
- npm-dist-tag(1)
- npm-login(1)
- npm-whoami(1)
- npm-doctor(1)
- npm-install(1)
- npm-run-script(1)
- npm-exec(1)
- npm-repo(1)
- npm-docs(1)
- npm-shrinkwrap-json(5)
- npm-edit(1)
- npm-stop(1)
- npm-diff(1)
- npm-find-dupes(1)
- npm-profile(1)
- npm-start(1)
- pacote(1)
- npm-ci(1)
- npm-stars(1)
- npm-update(1)
- npm-ping(1)
- npm-pack(1)
- npm-help-search(1)
- npm-prune(1)
- npm-org(1)
- npmrc(5)
- npm-audit(1)
- npm-unstar(1)
- arborist(1)
- npm-prefix(1)
- npm-publish(1)
- npm-config(1)
- npm-pkg(1)
- npm-adduser(1)
- npm-version(1)
- npm-completion(1)
- npm-install-test(1)
- npm-uninstall(1)
- npm-team(1)
- npm-help(1)
- npm-install-ci-test(1)
- npm-cache(1)
- npm-explore(1)
- npm-link(1)
- npm-root(1)
- package-json(5)
- npm-dedupe(1)
- npm-rebuild(1)
- npm-hook(1)
- npm-ls(1)
- npm-unpublish(1)
- npm-init(1)
- npm-restart(1)
- npm-outdated(1)
- npx(1)
- npm-access(1)
- npm-deprecate(1)
- npm-fund(1)
- npm-query(1)
- npm-owner(1)
- npm-test(1)
- npm-search(1)
- npm-token(1)
- npm-view(1)
- npm(1)
- node-npmcli-package-json
- node-libnpmpublish
- node-libnpmhook
- node-npm-packlist
- node-npmcli-installed-package-contents
- node-libnpmorg
- node-libnpmsearch
- node-npmcli-arborist
- node-npmcli-metavuln-calculator
- node-npmcli-mock-registry
- node-npmcli-disparity-colors
- node-npmcli-config
- node-pacote
- node-libnpmpack
- node-npmcli-map-workspaces
- node-libnpmaccess
- npm
- node-npmcli-smoke-tests
- node-libnpmversion
- node-npmcli-query
- node-libnpmteam
- node-npmcli-name-from-folder
- node-libnpmfund
- node-npmcli-promise-spawn
- node-libnpmdiff
- node-npmcli-run-script
- node-qrcode-terminal
- node-npmcli-node-gyp
- node-npmcli-git
- node-libnpmexec
apt-get install npm
Manual
| NPM-FUND(1) | General Commands Manual | NPM-FUND(1) |
NAME
npm-fund
Synopsis
<!-- AUTOGENERATED USAGE DESCRIPTIONS -->
Description
This command retrieves information on how to fund the dependencies
of a
given project. If no package name is provided, it will list all
dependencies that are looking for funding in a tree structure, listing
the type of funding and the url to visit. If a package name is provided
then it tries to open its funding url using the
--browser config param; if there are multiple
funding sources for the package, the user will be instructed to pass the
--which option to disambiguate.
The list will avoid duplicated entries and will stack all packages
that
share the same url as a single entry. Thus, the list does not have the
same shape of the output from npm ls.
Example
Workspaces support
It's possible to filter the results to only include a single
workspace
and its dependencies using the
workspace config option.
Example:
Here's an example running npm fund in a project with a
configured
workspace a:
$ npm fund test-workspaces-fund@1.0.0 +-- https://example.com/a | | `-- a@1.0.0 | `-- https://example.com/maintainer | `-- foo@1.0.0 +-- https://example.com/npmcli-funding | `-- @npmcli/test-funding `-- https://example.com/org
`-- bar@2.0.0
And here is an example of the expected result when filtering only
by a
specific workspace a in the same project:
$ npm fund -w a test-workspaces-fund@1.0.0 `-- https://example.com/a
| `-- a@1.0.0
`-- https://example.com/maintainer
`-- foo@2.0.0
Configuration
<!-- AUTOGENERATED CONFIG DESCRIPTIONS -->
See Also
- package spec
- npm install
- npm docs
- npm ls
- npm config
- npm workspaces
| May 2024 | 9.2.0 |