npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

zelda

v3.4.2

Published

Automatically `npm link` all your packages together!

Downloads

40

Readme

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 [email protected]:feross/webtorrent.git
  1. Clone the project dependencies you plan to work on.
git clone [email protected]:feross/bittorrent-protocol.git
git clone [email protected]:feross/bittorrent-swarm.git
git clone [email protected]: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.