You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> javascript.util@0.12.10 install D:\sources\temp\node_modules\javascript.util
> grunt
Running "bower:install" (bower) task
>> Installed bower packages
Running "closureDepsWriter:main" (closureDepsWriter) task
Executing: python bower_components/closure-library/closure/bin/build/depswriter.py --root_with_prefix="src ../../../../src" --output_file=deps.js
>> Error: Command failed: C:\Windows\system32\cmd.exe /s /c "python bower_components/closure-library/closure/bin/build/depswriter.py --root_with_prefix="src ../../../../src" --output_file=deps.js"
>> 'python' is not recognized as an internal or external command,
>> operable program or batch file.
>> FAILED to run command for target: main
Warning: Task "closureDepsWriter:main" failed. Use --force to continue.
Aborted due to warnings.
npm ERR! javascript.util@0.12.10 install: `grunt`
npm ERR! Exit status 3
npm ERR!
npm ERR! Failed at the javascript.util@0.12.10 install script.
npm ERR! This is most likely a problem with the javascript.util package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! grunt
npm ERR! You can get their info via:
npm ERR! npm owner ls javascript.util
npm ERR! There is likely additional logging output above.
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\ProgramData\\Chocolatey\\lib\\nodejs.commandline.0.12.0\\tools\\node.exe" "C:\\ProgramData\\chocolatey\\lib\\npm.1.4.9\\tools\\node_modules\\npm\\bin\\npm-cli.js" "install" "javascript.util"
npm ERR! cwd D:\sources\temp
npm ERR! node -v v0.12.0
npm ERR! npm -v 1.4.9
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! D:\sources\temp\npm-debug.log
npm ERR! not ok code 0
The text was updated successfully, but these errors were encountered:
I assume this is related to #10 somehow
The text was updated successfully, but these errors were encountered: