It seems that links to binaries are created for:
but not for locally installing the current package.
It would be useful if the local installation and global installation would be as similar as possible (apart from the installation path). The current difference is particularly cumbersome because of the missing shell wrappers on windows, without which local JS scripts get misinterpreted (run by scripting host instead of nodejs). So one can only really test commandline tools with global installs.
Is this still a problem for you?
I believe this behavior (global links created for global packages and ./node_modules/.bin local links created for local dependencies) is by design.
When you talk about "locally installing the current package", do you mean running npm install in the package directory? That has a different behavior from installing a dependency, because it also causes the devDependencies to be installed. However, you might get what you're hoping for with npm link in a package directory -- this should create global bin commands, although I'm not sure about Windows.
We are trying to clean up older npm issues, so if we don't hear back from you within a week, we will close this issue. (Don't worry -- you can always come back again and re-open it!)
As a follow-up to your original question, where would the links to binaries go?
When I install globally, they go to node's bin directory.
When I install a dependency, they go into the parent's node_modules/.bin directory.
When I do npm install in a package, where should its bin links go?
Closing as abandoned!