Grunt's mistake is because it tries to execute two commands connected by a double ampersand and && .
This is a bug that appears in grunt-exec 2.0.0 . Upgrading to 3.0.0 did not help me, but downgrading to ~1.0.0 fixed the problem.
Modify package.json so that the line for grunt-exec reads:
"grunt-exec": "~1.0.0",
Then run npm-update to download an older version of the package. After that, Grunt should work.
source share