npm published cli package's default install missing the `-g` flag

What I Wanted to Do

  1. npm published cli packageā€™s default install should be auto add the -g flag,

  2. at least give the author manually set -g flag rights

  3. recommends add a new cli params in package.json file with a boolean value

What Happened Instead

see the screen shortcut

npm pulished cli packageā€™s default install missing the -g flag

Reproduction Steps

see above screen shortcut

Details

  1. npm pulished cli packageā€™s default install should be auto add the -g flag,

  2. at least give the author manually set -g flag rights

  3. recommends add a new cli params in package.json file with a boolean value

Platform Info

$ npm --versions
{ npm: '6.4.1',
  ares: '1.15.0',
  cldr: '33.1',
  http_parser: '2.8.0',
  icu: '62.1',
  modules: '64',
  napi: '3',
  nghttp2: '1.34.0',
  node: '10.15.3',
  openssl: '1.1.0j',
  tz: '2018e',
  unicode: '11.0',
  uv: '1.23.2',
  v8: '6.8.275.32-node.51',
  zlib: '1.2.11' 
}
$ node -p process.platform
win32

Hi,

npmjs does not read your readme to change the install command on the right side because in general the packages are locally installed.

People normally read the readme instructions and there is preferGlobal but all of this has no effect on the information on the right side.

This is not a bug imo.

1 Like

(I agree with @DanielRuf, not a bug as such, moved to #support. If you want to propose this behaviour, then could go in #ideas?)