Unknown command 'cr'

[gkatsanos]

~/frontend   master $  npm install complexity-report      Mon Jun 18 10:31:07 2018
npm WARN [email protected] requires a peer of sinon@>=2.1.0 <5 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of sinon@^4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN The package es6-promise is included as both a dev and production dependency.
npm WARN The package oauth-signature is included as both a dev and production dependency.

+ [email protected]
added 5 packages from 26 contributors in 26.249s
 ~/frontend   master *$  cr ./                     29.7s  Mon Jun 18 10:31:39 2018
fish: Unknown command 'cr'
 !  ~/frontend   master *$  cr                            Mon Jun 18 10:31:58 2018
fish: Unknown command 'cr'

 ~/frontend   master *$  node -v                   16.5s  Mon Jun 18 10:33:56 2018
v9.5.0

[73rhodes]

To make the cr command available it needs to be in your PATH. You can either install it globally using npm -g install complexity-report (see NPM documentation for installing packages globally) or you can add ./node_modules/.bin to your PATH environment variable (see this example).

[73rhodes]

This is a duplicate of #26

[MilesHeise]

I struggled with this for a while too, before coming and looking for existing issues. This should be added to the readme, it is misleading how it currently appears that cr should just work and leads one to believe the problem is on your own machine