Potential bug - missing node_modules/.bin directory, after yarn add <package>

[ORESoftware]

mkdir foo && cd foo && yarn add <package>

will create three items in foo:

foo/
  package.json
  node_modules/
  yarn.lock

however if we cd into node_modules

cd node_modules && ls -a

there does not seem to be a .bin directory, which normally houses the command line utilities.

Is this an expected omission or is this a bug?

On the other hand, if we did

mkdir foo && cd foo && npm install <package>

there would be a

./node_modules/.bin directory present

[wyze]

If the package doesn't provide an executable, then the directory wouldn't be created until one does. In the issue template it asks to provide steps to reproduce and versions of Node, OS, Yarn. So please do that, and give exact steps to reproduce. Like yarn add left-pad instead of yarn add <package>.

[ORESoftware]

Sure will do, try this:

mkdir foo && cd foo && yarn add suman-home

when I ran this, I did not get a ../foo/node_modules/.bin directory

but when I do

mkdir foo && cd foo && npm install suman-home

I do get a ../foo/node_modules/.bin directory

If you look at the suman-home project, it has babel and istanbul, which have executables...

[wyze]

I see. That package itself doesn't expose an executable but it's dependencies do. You will want to wait for #2053 to land.

Going to close this as duplicate of #760.

[ORESoftware]

Thanks I understand the issue, appreciate your work

…

On Dec 4, 2016 12:16 PM, "Neil Kistner" ***@***.***> wrote: Closed #2135 <#2135>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2135 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKn56CBGFtBZgl3_6Izmrj6Wsd5ODTLrks5rEx-cgaJpZM4LDh2Y> .