.("""") (j)(_(_ __(_ ) (n o d e)_ _ _ _ / / / (n) (s)))`)`) ___ )L __ __ / / / n \|/ \|/((,(,' ((_( (( (('(| n \|/ | |
Part of the Node Water collection.
Useful if you are growing your node project, with or without any other node water.
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.
and if they are staged to be committed by git (e.g.
The problem lmc really solves is when you are:
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.
Official releases can be obtained from:
npm install -g linked-module-checker
The lastest developed code may node have not have been released, but can always be found from:
See the output of lmc --help
Add this to you git pre-commit: