[CB-13902] prepare-platform-release-branch: `grunt` dependency is unclear

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: cordova-coho
• Assignee: Unassigned
• Reporter: Jan Piotrowski (janpio)
• Created: 19/Feb/18 18:48
• Updated: 20/Feb/18 10:08

Description

Seems `coho prepare-platform-release-branch` needs grunt to be installed globally:

C:\Projects\Cordova\cordova-windows (6.0.x -> origin) (cordova-windows@6.0.0)
λ coho prepare-platform-release-branch --version 6.0.0 -r windows
Running from C:\Projects\Cordova
cordova-windows/ =============== Executing: git remote update origin
cordova-windows/ =============== Executing: git branch -r --list origin/master
  origin/master
cordova-windows/ =============== Already up-to-date: cordova-windows
cordova-windows/ =============== Executing: git branch -r --list origin/6.0.x
cordova-windows/ =============== Executing: git checkout 6.0.x
Already on '6.0.x'
cordova-js/ ==================== Executing: git remote update origin
cordova-js/ ==================== Executing: git branch -r --list origin/master
  origin/master
cordova-js/ ==================== Already up-to-date: cordova-js
cordova-js/ ==================== Executing: grunt compile:windows --platformVersion=6.0.0
(node:8516) UnhandledPromiseRejectionWarning: Error: grunt: Command failed with exit code ENOENT
    at ChildProcess.whenDone (C:\Projects\Cordova\cordova-coho\src\superspawn.js:144:23)
    at ChildProcess.emit (events.js:160:13)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:207:12)
    at onErrorNT (internal/child_process.js:389:16)
    at process._tickCallback (internal/process/next_tick.js:152:19)
(node:8516) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 13)
(node:8516) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

This isn't mentioned anywhere or at least I couldn't find it.