Do you want to request a feature or report a bug?
BUG
What is the current behavior?
Inside an (isolated) nave environment (node 6.9.2), yarn add global bower does not seem to install bower (or at least it cannot be found).
$(yarn global bin) _is_ in my $PATH!
If the current behavior is a bug, please provide the steps to reproduce.
$ ./nave use yarntest2 6.9.2
Creating new env named 'yarntest2' using node 6.9.2
Loading custom bashrc
Loading git completion
[yarntest2] $ npm install -g yarn
npm WARN deprecated [email protected]: It is recommended to install Yarn using the native installation method for your environment. See https://yarnpkg.com/en/docs/install
/home/ivo/.nave/installed/yarntest2/bin/yarn -> /home/ivo/.nave/installed/yarntest2/lib/node_modules/yarn/bin/yarn.js
/home/ivo/.nave/installed/yarntest2/bin/yarnpkg -> /home/ivo/.nave/installed/yarntest2/lib/node_modules/yarn/bin/yarn.js
(...)
[yarntest2] $ yarn global bin
/home/ivo/.nave/installed/yarntest2/bin
[yarntest2] $ yarn add global bower
yarn add v0.17.10
warning No license field
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved 2 new dependencies.
鈹溾攢 [email protected]
鈹斺攢 [email protected]
warning No license field
Done in 0.91s.
[yarntest2] $ type bower
bash: type: bower: not found
[yarntest2] $ yarn global bin
/home/ivo/.nave/installed/yarntest2/bin
[yarntest2] $ echo $PATH
/home/ivo/.nave/installed/yarntest2/bin:(..remainder..)
clearing ~/.cache/yarn and/or yarn.lock seems to have no effect.
(some) other global packages seem to work (e.g. ember-cli). phantomjs might also be failing (but that may be a different issue)
What is the expected behavior?
To have bower globally installed, similar to npm install -g
Please mention your node.js, yarn and operating system version.
node: 6.9.2 (through nave)
yarn: 0.17.10
PEBKAC: right command is yarn global add not yarn add global
Most helpful comment
PEBKAC: right command is
yarn global addnotyarn add global