This requires a few fixes to build.js, which will no doubt cause some annoying backwards incompatibility issues. It's worth it, though, because having the "dependson" folder clears up a lot of edge cases and makes this more straightforward. Also, it's broken already, so nothing is really lost :)
This is different than the "dependencies" folder. That folder is for linking in modules. However, there may be a case where a package exposes no main or lib, but is nevertheless required by some other package. (Perhaps it uses its CLI executable or something.) Also, having a link to the dependency's package dir is SUPER handy, as it makes uninstallation much simpler, which is very helpful in fixing #92
Good thing no one was relying on that feature, or they would have hit that bug.
Now, the dependency/dependent linking happens *after* all of the other stuff in the build process.
…n the future)