npm check-dependencies

[netweb]

Via ​#BuddyPress6756

I think we should introduce the check-dependencies NPM package into our Grunt workflow. It checks if currently installed NPM dependencies are the same versions that are specified in the package.json.

whether it's a version bump or a new package, one can forget to invoke npm install (or bower install) and continue using the application, possibly encountering errors caused by obsolete package versions. To avoid it, use the check-dependencies module at the top of the entry point of your application; it will inform about not up-to-date setup and optionally install the dependencies.

​https://github.com/mzgol/check-dependencies

[netweb]

In 5964:

Tools: Add the grunt-check-dependencies npm module.

This changeset adds the Grunt task checkDependencies via ​https://www.npmjs.com/package/grunt-check-dependencies to check the currently npm installed modules against the required modules semantic version listed in package.json, if the check fails a prompt to update installed npm modules is displayed and is required before other Grunt tasks can be run.

Run npm install after updating your repo to install the module and task.

Props netweb.
Fixes #2893.