FWIW, this issue was likely due to using an outdated version of Node. The script is being updated to detect this scenario.