What is the current behavior?
Linking to a global module target
does not create links to target
's bin entries as specified in target
's package.json
.
Steps to reproduce
$ pwd
/home/ravi/.config/yarn/global/node_modules/ethereumjs-testrpc-sc
$ yarn link
yarn link v1.1.0
success Registered "ethereumjs-testrpc-sc".
info You can now run `yarn link "ethereumjs-testrpc-sc"` in the projects where you want to use this module and it will be used instead.
Done in 0.07s.
$ grep -A2 bin package.json
"bin": {
"testrpc-sc": "./build/cli.node.js"
},
$ mkdir ~/tmp/pkg && cd ~/tmp/pkg
$ yarn init
yarn init v1.1.0
question name (pkg):
question version (1.0.0):
question description:
question entry point (index.js):
question repository url:
question author:
question license (MIT):
question private:
success Saved package.json
Done in 4.05s.
$ yarn link ethereumjs-testrpc-sc
yarn link v1.1.0
success Using linked module for "ethereumjs-testrpc-sc".
Done in 0.07s.
$ ls -la node_modules/.bin
ls: cannot access 'node_modules/.bin': No such file or directory
$
What is the expected behavior?
I expect that ~/tmp/prj/node_modules/.bin/testrpc-sc
is a symlink to .config/yarn/global/node_modules/ethereumjs-testrpc-sc/build/cli.node.js
Please mention your node.js, yarn and operating system version.
$ node --version
v8.5.0
$ yarn --version
1.1.0
$ uname -a
Linux svelte 4.9.51-1-MANJARO #1 SMP PREEMPT Wed Sep 20 10:37:40 UTC 2017 x86_64 GNU/Linux
I am running into the same problem +1
+1
Same here.
npm 5.6.0
yarn 1.7
Same here
$ npm --version
6.2.0
$ yarn --version
1.9.4
I would recommend giving whitecolor/yalc a try.
Most helpful comment
I am running into the same problem +1