Skip to content

Latest commit

 

History

History
76 lines (51 loc) · 2.45 KB

README.md

File metadata and controls

76 lines (51 loc) · 2.45 KB

zelda travis npm downloads javascript style guide

Automatically npm link all your packages together!

link spin attack

Sometimes Link needs a little help from Zelda.

usage

  1. Install it globally.
npm install -g zelda
  1. Run zelda from your node project directory. For example:
cd ~/code/my-project
zelda

zelda finds all the node packages in your code folder (~/code/ in the example). If any of these packages are listed as a dependency in the nearest package.json of your working directory, it automatically symlinks it for you.

Zelda assumes that all your code lives in the directory one level up from the folder where you run zelda. So, keep all your packages in a single folder like ~/code and run zelda inside one of the projects (ex: ~/code/my-project).

what you might do if you're clever

  1. Clone a cool project.
mkdir ~/code
cd ~/code
git clone git@github.com:feross/webtorrent.git
  1. Clone the project dependencies you plan to work on.
git clone git@github.com:feross/bittorrent-protocol.git
git clone git@github.com:feross/bittorrent-swarm.git
git clone git@github.com:feross/bittorrent-dht.git
  1. Recursively npm install all project dependencies, but npm link the ones that are local.
cd webtorrent
zelda

Gone are the days of running tons of npm link commands by hand!

features

  • Automatically npm link all your modules together
  • Supports dependencies, devDependencies, and optionalDependencies
  • Recursively runs npm install so your freshly cloned projects are ready to go!

link is better with zelda!

link

license

MIT. Copyright Feross Aboukhadijeh.