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-link-check

v5.0.1

Published

CLI utility that checks whether a project's current node modules tree contains npm-link'ed packages

Downloads

2,939

Readme

npm-link-check

npm version

example workflow Coverage Status

CLI utility that checks whether a project's current node modules tree contains npm-link'ed packages.

So that you don't build a distributed bundle containing linked packages ever again!

npm-link-check even works with npm scoped packages. Big ups @Istenes for that PR :beers:

Install

# for CLI use:
npm install -g npm-link-check

# for npm-script use:
npm install npm-link-check

Usage

CLI

# to check current working directory
npm-link-check

# to check arbitrary project
npm-link-check path/to/project/root

npm-link-check will log something like:

Some npm-link\'ed packaged were found:
    - package dummy (at node_modules/dummy) is linked

and exit with code 1 if one or many packages npm-link'ed are found. Big ups to @c-eliasson for cleaning that up!

As a pre-version check

In this era of bundled and transpiled javascript, it is common for projects to build a distributed version when running the npm version task. Using npm-link-check, the often neglected check for npm-link'ed packages can automated as follow:

In your project's package.json, add:

{
  "scripts": {
    "preversion": "npm-link-check"
  }
}

making npm-link-check run on npm version before your package's version is bumped. If an npm-link'ed package if found, the npm version task will be aborted.

Credits

2024 Étienne Tétreault-Pinard. MIT License

Standard - JavaScript Style Guide