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

npm-autolink

v1.0.0

Published

Npm link done right, automatically create symlinks between your workspace projects

Downloads

16

Readme

npm-autolink

Npm link done right

Npm Npm dependencies Linux Build Windows Build Coverage

Description

When developping multiple node modules it is cumbersome to publish one module to test it in other modules. Npm link is handy in these cases but can be a bit slow (everything is installed globally) and doesn't cover everything.

Npm-autolink come to the rescue by permitting direct links between dev folders.

Main features are :

  • Define your workspace modules links in autolink.json file.
  • Automatically link or unlink all projects at once
  • bin executables are also linked !

Breaking change in v1

V1 of npm-autolink works very differently than v0 :

  • only one conf file is loaded autolink.json
  • you can link and unlink many projects at the same time

Tests are coming ...

Installation

npm install -g npm-autolink

autolink.json file

  • describe linked projects in your workspace
  • npm link will only link those projects

Example autolink.json file:

{
  "link": {
    "@iamasoft/project1": ["@iamasoft/lib1"],
    "@iamasoft/lib1": ["@iamasoft/lib2"],
  }
}

Note : node_modules and bower_components folders are never scanned.

Usage

npmauto [command] [options]

Print usage information

$ npmauto -h
$ npmauto --help

List all detected packages in workspace and their states

$ npmauto ls

Link all

$ npmauto link

Unkink all

$ npmauto unlink