npm displays an informational message reminding developers that some of their installed package dependencies have defined funding sources and are seeking financial support. This is not an error—it's a community-driven way for open-source maintainers to request voluntary contributions.
npm displays this message to remind developers that some of their installed package dependencies have defined funding sources (GitHub Sponsors, Open Collective, Tidelift, etc.) and are seeking financial support from users. This is not an error or warning—it's a community-driven way for open-source maintainers to request voluntary contributions. The message appears after successful package installation; your installation completed normally and is unaffected. The funding feature was introduced in npm v6.13 to help maintainers request voluntary contributions for open-source work.
The 'packages are looking for funding' message is not an error or warning—your packages installed successfully. This is npm's polite reminder about available funding opportunities. Your build will complete normally and is unaffected.
If you only want to hide the message temporarily for one command, use the --no-fund flag:
npm install --no-fund
npm update --no-fundThis works with any npm command that would normally show funding messages.
For a single project, create or edit .npmrc in your project root and add:
fund=falseThis applies only to the current project and will suppress funding messages for all npm commands in that directory.
To suppress funding messages across all projects on your machine, set the global npm configuration:
npm config set fund false --globalThis adds fund=false to your ~/.npmrc file and affects all npm commands globally.
In CI/CD pipelines or containerized environments, set an environment variable instead:
export NPM_CONFIG_FUND=falseThen run your npm commands normally. This approach is useful for Docker containers and GitHub Actions workflows.
If you want to learn about which packages are seeking funding, run:
npm fundThis shows all dependencies looking for funding in a tree structure with URLs. You can also check a specific package with:
npm fund [package-name]Not a true warning: The funding functionality is independent of package installation; disabling it does not affect dependency resolution or build success.
Some packages bypass npm's system: Some packages with postinstall scripts (like Parcel) display their own funding messages even with --no-fund enabled—in these cases, you may need to suppress output at a higher level in your CI/CD pipeline.
Alternative package managers: Yarn and pnpm handle funding notifications differently and do not display npm's funding messages.
npm ERR! code E401 npm ERR! 401 Unauthorized - Token has expired
Token has expired - npm authentication failure
npm ERR! code ENOAUDIT npm ERR! Audit endpoint not supported
How to fix "npm ERR! code ENOAUDIT - Audit endpoint not supported"
npm ERR! code EBADDEVENGINES npm ERR! devEngines.runtime incompatible with current node version
How to fix "npm ERR! code EBADDEVENGINES - devEngines.runtime incompatible with current node version"
npm ERR! code EAI_NODATA npm ERR! errno EAI_NODATA npm ERR! getaddrinfo EAI_NODATA registry.npmjs.org
How to fix "npm ERR! code EAI_NODATA - getaddrinfo EAI_NODATA"
npm ERR! code ETOOMANYARGS npm ERR! Too many arguments
How to fix "npm ERR! code ETOOMANYARGS - Too many arguments"