Repository navigation
[BUG] Global install shows funding message but can't get info #3112
Description
Current Behavior:
bjornstar@penguin:~$ npm i -g npm
changed 14 packages, and audited 253 packages in 14s
11 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
bjornstar@penguin:~$ npm fund
bjornstar
bjornstar@penguin:~$ npm -g fund
npm ERR! code EFUNDGLOBAL
npm ERR! `npm fund` does not support global packages
npm ERR! A complete log of this run can be found in:
npm ERR! /home/bjornstar/.npm/_logs/2021-04-21T01_32_23_134Z-debug.log
bjornstar@penguin:~$ npm fund npm
npm ERR! code ENOFUND
npm ERR! No valid funding method available for: npm
npm ERR! A complete log of this run can be found in:
npm ERR! /home/bjornstar/.npm/_logs/2021-04-21T01_37_39_995Z-debug.log
Expected Behavior:
Either show me the funding info or don't tell me there are packages looking for funding.
It's poor user experience for the application to suggest running commands to users that do not work.
This is similar to #2862
Steps To Reproduce:
npm i -g npm
Environment:
- Node: v14.16.0
- npm: 7.10.0
Activity
ljharb commentedon Apr 21, 2021
npm fund -gshould definitely work imo.darcyclarke commentedon Jun 4, 2021
npm fundin output post-install w/-gIf you'd like
npm fund -gto work, that is a separate feature request.ljharb commentedon Jun 4, 2021
@darcyclarke i'm not sure why it should be - imo every command should work both with or without
-g(when reasonable), or else it's a bug.fix: don't print the funding message for global installs (#9864)