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

linked-module-checker

v0.0.10

Published

Help node.js module development flow more freely

Downloads

5

Readme

                                 .("""")                                      (j)
                               (_(_ __(_ )                                 (n o d e)
 _ _ _       _                   / / /                       (n)              (s)
 ))`)`) ___  )L __ __           / / /           n            \|/              \|/
((,(,' ((_( (( (('(|             n             \|/            |                |

Linked Module Checker

Preamble

Node water to help node.js module development flow more freely. Useful if you are growing your node project, with or without any other node water.

So What Does it Do?!

It checks the modules in your node_moudles directory and reports on their status, specifically if they are linked (e.g. npm linked) or installed (e.g. npm installed) and if they are staged to be committed by git (e.g. git added).

The problem lmc really solves is when you are:

  1. npm linking your modules during development; and
  2. git committing your node_moudles directory; and
  3. bored of needing to switch to and from linked vs installed modules each time you git commit.

Is This Really A Problem I Need To Worry About?

Maybe not, but you've read this far so read on...

Splitting your node.js project into modules is a good thing. npm linking modules during development can really save you time. git committing your node_modules is also a good thing as Mikeal Rogers neatly summaries.

However if you accidentally git commit your node modules while they are npm linked your source code won't be in a great state. The symlinks created by npm link are unlikely to work on any machine other than your own so when you git clone/pull/push your project somewhere else it is unlikely to run without some manual npm tinkering first. Even worse, unless you have done some diligent publishing of your module elsewhere it may not be possible to get hold of the right version to make your project run at all.

lmc helps you avoid these problems.

Help

See the output of lmc --help

Integration with Git

Add this to you git pre-commit:

`lmc -e`

Credits

  • Isaac Z. Schlueter - https://github.com/isaacs/npm