Package Exports
- zelda
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (zelda) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
zelda 
Automatically npm link all your packages together!
Sometimes Link needs a little help from Zelda.
usage
- Install it globally.
npm install -g zelda- Run
zeldafrom your node project directory. For example:
cd ~/code/my-project
zeldazelda 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
- Clone a cool project.
mkdir ~/code
cd ~/code
git clone git@github.com:feross/webtorrent.git- 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- Recursively
npm installall project dependencies, butnpm linkthe ones that are local.
cd webtorrent
zeldaGone are the days of running tons of npm link commands by hand!
features
- Automatically
npm linkall your modules together - Supports
dependencies,devDependencies, andoptionalDependencies - Recursively runs
npm installso your freshly cloned projects are ready to go!
link is better with zelda!
license
MIT. Copyright Feross Aboukhadijeh.