-
Notifications
You must be signed in to change notification settings - Fork 3k
bin/files are automatically symlinked? #739
Comments
It could be because you have |
no, directories prop is not in use too ... first I found this in sharedjs package ... now tested some other, all of them have this problem. if I use bin: {} then it stops doing that. |
Ah, yeah, it's defaulting the "bin" directory to "./bin" if there's a dir by that name. I'm going to rip that out for 1.0 |
is this behaviour being there all the time? |
so, if we have bin dir and don't want to symlink its files, we have to use bin: {} ... puh this is really broken :) |
It's not really broken. Worst case scenario, it creates some symlinks that you don't need. In the vast majority of packages, putting something in a "bin" folder is grounds for believing it's an executable. Changed in 1.0. |
also if doing this automatically, package name should be used as a prefix for the symlink name, f.e package fui, bin/test.js symlinked to fui-test. I got problems because I have file names conflicts .... |
on dbf5e80, more specifically. |
I don't use "bin" key in package.json, but I see, that all files from bin are symlinked to /usr/local/bin
How is that possible?
MacOS 10.6.6
Node 0.4.0
npm 0.3.17
Oleg
The text was updated successfully, but these errors were encountered: