Using npm link <package> instead of ln -s

This is how I would suggest people get started. Use `npm`'s built in functionality instead of using `ln -s`. 
If a dev adds a bin to cabbage and they've linking it, it'll be globally available to that dev but not for normal users, and this could lead to an accidental divergence. 


I would prefer cabbage devs don't have a globally reachable cabbage module, only cabbage-cli.  local vs global is incredibly confusing to most people I've worked with in node in practice and I want to be abundantly consistent that the cabbage module not be installed globally

On Tue, Dec 9, 2014 at 7:06 PM, Travis Smith <notifications@github.com>
wrote:

>> @@ -47,14 +47,16 @@ git clone git@github.com:cabbagejs/blueprint-simple.git
>>  
>>  cd cabbage
>>  npm install
>> +npm link
> I completely don't understand the risk you are suggesting. It's only for people hacking on cabbage (limited set of cabbage customers), and if you `npm install` without calling `npm link cabbage` you'll get the npm package instead of the linked directory. `npm link cabbage` creates a symlink to `<npm-cache>/node_modules/cabbage` which is symlinked to `../../cabbage`. So I'm guessing you've experienced some annoying case that hasn't reared it's head in my world. 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/cabbagejs/cabbage/pull/26/files#r21574551