571

I usually get "x packages are looking for funding." when running npm install on a react project. Any idea what that means?

1
  • 11
    Moderator Note: This question is now being discussed on Meta. Please take all discussion about whether or not it is on-topic there, instead of leaving comments here. Commented Jan 29, 2020 at 19:53

10 Answers 10

857

When you run npm update in the command prompt, when it is done it will recommend you type a new command called npm fund.

When you run npm fund it will list all the modules and packages you have installed that were created by companies or organizations that need money for their IT projects. You will see a list of webpages where you can send them money. So "funds" means "Angular packages you installed that could use some money from you as an option to help support their businesses".

It's basically a list of the modules you have that need contributions or donations of money to their projects and which list websites where you can enter a credit card to help pay for them.

6
  • 38
    Note that this a npm feature, it's not specific to Angular. You would get that same message with React or Vue or anything else.
    – alcfeoh
    Commented Aug 14, 2020 at 19:04
  • 106
    Up until now I thought npm fund did something regarding dependency resolution. So this answer gets an upvote. Commented Sep 18, 2020 at 21:42
  • 2
    Interesting. I really thought of it when read the message, but googled it just to be sure Commented Jan 17, 2022 at 8:14
  • 9
    Same here. I think most of the people who use node also thought that npm fund will fix some issues regarding package dependency. Commented Feb 13, 2022 at 7:02
  • I'm going around in circles trying to setup a CLI dev kit plagued with warnings galore and this finding out this isn't something that impacts it is such a HUGE relief. Thank you!
    – donyd
    Commented Feb 11 at 14:39
193

npm decided to add a new command: npm fund that will provide more visibility to npm users on what dependencies are actively looking for ways to fund their work.

npm install will also show a single message at the end in order to let user aware that dependencies are looking for funding, it looks like this:

$ npm install
packages are looking for funding.
run `npm fund` for details.

Running npm fund <package> will open the url listed for that given package right in your browser.

For more details look here

5
  • 31
    npm is a package manager, and as such it should stick to the managing packages business, not to "make visibile people requesting funds". That should be another command, something like "show-who-need-funds" Commented May 22, 2020 at 10:26
  • 45
    @GianlucaGhettini The problem was that existing packages were already printing messages asking for funding/donations during the install process. Having npm print a single message was determined to be far nicer than having say 20 different packages each print their own request for donations. Pretty much the only options were: adding this feature, letting packages continue to print their own message, or banning such messages without providing any alternative. They did not really want to annoy package developers by imposing the last option, so they want with the first. Commented Jun 16, 2020 at 11:22
  • 6
    @GianlucaGhettini I think requesting funds from a package is also part of managing the package, so npm is not doing so wrong with this feature. Commented Mar 17, 2021 at 22:55
  • 7
    @ErisanOlasheni I think managing a package means installing/unsinstalling/updating a package. End of story. Have you ever seen the "ls" Linux command asking to also do something else like creating, deleting, renaming a file? Commented Mar 18, 2021 at 15:27
  • @Kevin Cathcart What's wrong with " letting packages continue to print their own message," I think keeping npm lighter-weight would be better, less is more secure and more reliable.
    – Zombies
    Commented May 26, 2023 at 16:18
180

First of all, try to support open source developers when you can, they invest quite a lot of their (free) time into these packages. But if you want to get rid of funding messages, you can configure NPM to turn these off. The command to do this is:

npm config set fund false --location=global

... or if you just want to turn it off for a particular project, run this in the project directory:

npm config set fund false 

For details why this was implemented, see @Stokely's and @ArunPratap's answers.

4
  • Well explained, you start nice: please support them, but hhmmm if I think right, ok forget about it, go your way and here is the trick;)
    – Timo
    Commented May 15, 2021 at 17:54
  • 13
    @Timo At first glance it might seem like that, but there are other reasons to turn this off. E.g. my company supports a couple of package authors, so there's no need to bother all my dev team with those messages on their screen every time they run an update. (We put fund=false in our project's .npmrc file for this.) Commented May 16, 2021 at 19:05
  • 5
    There's also the principle of the matter. I dislike the abusive tone I see creeping into open source culture - the taint of entitlement and resentment. It's not how it used to be. It's evident in the bolding of text in the above answers...
    – odigity
    Commented Jan 18, 2023 at 13:39
  • 2
    @odigity I wish I could +twice...
    – BillRuhl
    Commented Mar 17, 2023 at 19:04
36

You can skip fund using:

npm install --no-fund YOUR PACKAGE NAME

For example:

npm install --no-fund core-js

If you need to install multiple packages:

npm install --no-fund package1 package2 package3
8
  • 2
    alias npmi='npm install --no-fund'
    – Lauren Yim
    Commented Jul 5, 2020 at 12:16
  • 9
    Even better: alias npm='npm --no-fund'
    – mbomb007
    Commented Sep 3, 2020 at 21:22
  • 2
    Even better : echo "npmf='npm install --no-fund'" >> ~/.bash_aliases && source ~/.bash_aliases on Linux
    – mhannani
    Commented Sep 24, 2020 at 15:06
  • 7
    Even better: npm config set fund false --global (from Jeroen Landheer's answer to this question) Commented Oct 12, 2021 at 21:25
  • 4
    even better "uninstall node and npm"
    – Plochie
    Commented Jun 19, 2022 at 18:07
24

first, it's not an error or warning. it's basically a message to you to donate some money if you wish to the company/people or individual who built a package you have installed/used in your project, to see which package, simply type in your terminal

npm fund

and a list of the packages names and their website URLs underneath to donate. I hope this is helpful..

3

These are Open Source projects (or developers) which can use donations to fund to help support their business.

In npm the command npm fund will list the urls where you can fund

In composer the command composer fund will do the same.

While there are options mentioned above using which one can use to get rid of the funding message, but try to support the cause if you can.

2
npm fund [<pkg>]

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 in which are listed the type of funding and the url to visit.
The message can be disabled using: npm install --no-fund

2
npm install --silent

Seems to suppress the funding issue.

1
  • 4
    The question is not to suppress the message, it's to understand what it means! Commented Jan 16, 2022 at 13:32
1
npm config set false --global 
npm config set fund false
2
  • 10
    Welcome to StackOverflow. While these commands may answer the question, providing additional context regarding how and/or why they solves the problem would improve the answer's long-term value. Furthermore there is already an accepted answer... Commented Jul 9, 2021 at 22:39
  • 2
    this answer has an error, first command should be npm config set fund false --location=global instead (missed "fund" and used obsolete syntax) - also, no need to use the 2nd one if you're using the first.
    – user213769
    Commented Sep 2, 2022 at 15:24
-1

I would recommend against suppressing the funding message. It is informational only. At the very least they would give you some idea of one the potential risks that the 3rd party npm package is facing.

Not the answer you're looking for? Browse other questions tagged or ask your own question.