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

linkr

v0.1.0

Published

Utility for making npm link easier

Downloads

5

Readme

linkr

An npm package to make managing npm links easier.

Are you working on a sufficiently large NodeJS project with dependent projects that rely on each other? If so, then you are probably using npm link to make working with multiple local packages easier.

Installation

Install linkr globally using npm.

$ npm install -g linkr

Usage

Let's assume that you have a directory setup similar to the following example. Your foo-api project is your primary application, and it depends on both foo-caching and foo-models. While you might have been able to write this as one very large Node package, it was decided that there would be value if the foo-caching and foo-models projects could shared in multiple projects.

path/to/foo/
    foo-api/
        package.json
    foo-caching/
        package.json
    foo-models/
        package.json

In your foo-api/package.json, add a links section under config.

{
  "name": "foo-api",
  "version": "0.0.0",
  "dependencies": {
    "foo-caching": "~2.1.0",
    "foo-models": "~3.17.0"
  },
  "config": {
    "links": [
      "../my-project-caching",
      "../my-project-models"
    ]
  }
}

In your development environment, you will want to use symbolic links. You can now run linkr from the project root (i.e. the same folder that contains the package.json file).

$ cd path/to/foo/foo-api
$ linkr

Commands

link (default)

Run all prescribed npm links. This is the default command.

help

Show help text.

version

Show linkr version

remove

Remove symbolic links.