Grunt warning

Issue Summary

When running grunt commands, it serves a warning that

 Local Npm module "grunt-cli" not found. Is it installed?

Research in other repositories, such as https://github.com/backbone-boilerplate/backbone-boilerplate/issues/237 indicate that the fix is to relocate the grunt-cli dependency from devDependencies to peerDependencies in the package.json file. I have submitted relevant PR in the case that this is a correct solution.

Steps to Reproduce

npm install grunt

Technical details

• Ghost Version: master - latest commit: 2329edd
• Server OS: Ubuntu 13.10
• Node Version: v0.10.25

[shama]

Just chiming in here. grunt-cli should stay as a devDependencies. That way it is only installed when the user does a npm install from the project folder (and we are assuming developing Ghost itself).

peerDependencies are for user end dependencies the project indirectly relies on. Dependencies listed there would be installed when the user does a npm install packagename. Which we wouldn’t want end users installing grunt-cli, only developers.

dependencies are for user end dependencies the project directly relies on and also get installed when an end user does a npm install packagename.

The message Local Npm module "grunt-cli" not found. Is it installed? comes from attempting to grunt.loadNpmTasks('grunt-cli'). Grunt thinks you’re trying to load a grunt task but grunt-cli is not a grunt task, so it complains.

Avoid loading grunt-cli as a task with require('matchdep').filterDev(['grunt-*', '!grunt-cli']).forEach(grunt.loadNpmTasks); instead.

[ErisDS]

Fixed by #2218