Error on startup after latest Git Pull: package browserify does not satisfy its siblings' peerDependency requirements!

[jedimstr]

I'm getting these errors on startup after the latest git pull:

> miner-dashboard@0.4.0 start /home/jedimstr/miner-dashboard
> npm install --production && grunt compile && node app

npm WARN package.json rickshaw@1.4.6 No repository field.
npm ERR! peerinvalid The package browserify does not satisfy its siblings' peerDependencies requirements!

npm ERR! System Linux 3.8.13-bone32
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install" "--production"
npm ERR! cwd /home/jedimstr/miner-dashboard
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.3
npm ERR! code EPEERINVALID
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /home/jedimstr/miner-dashboard/npm-debug.log
npm ERR! not ok code 0

npm ERR! miner-dashboard@0.4.0 start: `npm install --production && grunt compile && node app`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the miner-dashboard@0.4.0 start script.
npm ERR! This is most likely a problem with the miner-dashboard package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm install --production && grunt compile && node app
npm ERR! You can get their info via:
npm ERR!     npm owner ls miner-dashboard
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 3.8.13-bone32
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! cwd /home/jedimstr/miner-dashboard
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.3
npm ERR! code ELIFECYCLE
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /home/jedimstr/miner-dashboard/npm-debug.log
npm ERR! not ok code 0

When I do a npm list -g to show the packages installed and see if there are any errors with them I get this (no errors):

root@matrix-openvpn:/home/jedimstr# npm list -g
/usr/local/lib
└─┬ npm@1.4.3
  ├── abbrev@1.0.4
  ├── ansi@0.2.1
  ├── ansicolors@0.3.2
  ├── ansistyles@0.1.3
  ├── archy@0.0.2
  ├── block-stream@0.0.7
  ├── child-process-close@0.1.1
  ├── chmodr@0.1.0
  ├── chownr@0.0.1
  ├── cmd-shim@1.1.1
  ├── columnify@0.1.2
  ├── editor@0.0.5
  ├── fstream@0.1.25
  ├─┬ fstream-npm@0.1.6
  │ └── fstream-ignore@0.0.7
  ├── github-url-from-git@1.1.1
  ├── github-url-from-username-repo@0.0.2
  ├── glob@3.2.7
  ├── graceful-fs@2.0.2
  ├── inherits@2.0.1
  ├── ini@1.1.0
  ├─┬ init-package-json@0.0.14
  │ └── promzard@0.2.1
  ├── lockfile@0.4.2
  ├── lru-cache@2.5.0
  ├─┬ minimatch@0.2.14
  │ └── sigmund@1.0.0
  ├── mkdirp@0.3.5
  ├── node-gyp@0.12.2
  ├── nopt@2.2.0
  ├── npm-install-checks@1.0.0
  ├── npm-registry-client@0.4.4
  ├── npm-user-validate@0.0.3
  ├─┬ npmconf@0.1.12
  │ └─┬ config-chain@1.1.8
  │   └── proto-list@1.2.2
  ├── npmlog@0.0.6
  ├── once@1.3.0
  ├── opener@1.3.0
  ├── osenv@0.0.3
  ├── path-is-inside@1.0.0
  ├─┬ read@1.0.5
  │ └── mute-stream@0.0.4
  ├── read-installed@1.0.0
  ├─┬ read-package-json@1.1.7
  │ └── normalize-package-data@0.2.9
  ├─┬ request@2.30.0
  │ ├── aws-sign2@0.5.0
  │ ├── forever-agent@0.5.0
  │ ├─┬ form-data@0.1.2
  │ │ ├── async@0.2.9
  │ │ └─┬ combined-stream@0.0.4
  │ │   └── delayed-stream@0.0.5
  │ ├─┬ hawk@1.0.0
  │ │ ├── boom@0.4.2
  │ │ ├── cryptiles@0.2.2
  │ │ ├── hoek@0.9.1
  │ │ └── sntp@0.2.4
  │ ├─┬ http-signature@0.10.0
  │ │ ├── asn1@0.1.11
  │ │ ├── assert-plus@0.1.2
  │ │ └── ctype@0.5.2
  │ ├── json-stringify-safe@5.0.0
  │ ├── mime@1.2.11
  │ ├── node-uuid@1.4.1
  │ ├── oauth-sign@0.3.0
  │ ├── qs@0.6.6
  │ ├─┬ tough-cookie@0.9.15
  │ │ └── punycode@1.2.3
  │ └── tunnel-agent@0.3.0
  ├── retry@0.6.0
  ├── rimraf@2.2.6
  ├── semver@2.2.1
  ├─┬ sha@1.2.3
  │ └── readable-stream@1.0.24
  ├── slide@1.1.5
  ├── tar@0.1.19
  ├── text-table@0.2.0
  ├── uid-number@0.0.3
  └── which@1.0.5

Do you see any that need to be re-installed to match the latest updates you've committed?

[selaux]

Hav you tried rm -r node_modules and then starting the dashboard again? To list your dependenciest for the project you just need to run npm list without -g

[jedimstr]

Cleaning up node_modules did the trick. Thanks!

On startup now it complains about:

>> Local Npm module "grunt-contrib-jshint" not found. Is it installed?
>> Local Npm module "grunt-mocha-test" not found. Is it installed?

So I went ahead and installed both modules... but I still get the same warnings when I start the dashboard again.

[selaux]

They don't need to be installed for running the dasboard, that's why they are specified as devDependencies. The warnings can be ignored...

[selaux]

NB: With current master, if you set the environment variable NODE_ENV to production you shouldn't get these warnings anymore.

[jedimstr]

Thanks again!