Angular.js: 'bower install' fail on Windows

Created on 21 Dec 2013  Â·  16Comments  Â·  Source: angular/angular.js

Hi, I'm trying to setup development environment for AngularJS and so I'm following the procedure described here. I keep getting an error with the command bower install relative to installation of a package called ng-closure-runner#*. Here is the full console log for the command:

C:\Users\gimmi\Sources\angular.js>bower install
bower bootstrap#*           not-cached https://raw.github.com/twbs/bootstrap/v2.0.2/docs/assets/bootstrap.zip#*
bower bootstrap#*              resolve https://raw.github.com/twbs/bootstrap/v2.0.2/docs/assets/bootstrap.zip#*
bower closure-compiler#*    not-cached https://closure-compiler.googlecode.com/files/compiler-20130603.zip#*
bower closure-compiler#*       resolve https://closure-compiler.googlecode.com/files/compiler-20130603.zip#*
bower ng-closure-runner#*   not-cached https://raw.github.com/angular/ng-closure-runner/v0.2.2/assets/ng-closure-runner.zip#*
bower ng-closure-runner#*      resolve https://raw.github.com/angular/ng-closure-runner/v0.2.2/assets/ng-closure-runner.zip#*
bower bootstrap#*             download https://raw.github.com/twbs/bootstrap/v2.0.2/docs/assets/bootstrap.zip
bower ng-closure-runner#*     download https://raw.github.com/angular/ng-closure-runner/v0.2.2/assets/ng-closure-runner.zip
bower closure-compiler#*      download https://closure-compiler.googlecode.com/files/compiler-20130603.zip
bower lunr.js#0.4.0             cached git://github.com/olivernn/lunr.js.git#0.4.0
bower lunr.js#0.4.0           validate 0.4.0 against git://github.com/olivernn/lunr.js.git#0.4.0
bower jquery#1.10.2             cached git://github.com/components/jquery.git#1.10.2
bower jquery#1.10.2           validate 1.10.2 against git://github.com/components/jquery.git#1.10.2
bower google-code-prettify#1.0.0           cached git://github.com/tcollard/google-code-prettify.git#1.0.0
bower google-code-prettify#1.0.0         validate 1.0.0 against git://github.com/tcollard/google-code-prettify.git#1.0.0
bower components-font-awesome#3.1.0        cached git://github.com/components/font-awesome.git#3.1.0
bower components-font-awesome#3.1.0      validate 3.1.0 against git://github.com/components/font-awesome.git#3.1.0
bower ng-closure-runner#*                 extract ng-closure-runner.zip
bower bootstrap#*                         extract bootstrap.zip
bower closure-compiler#*                  extract compiler-20130603.zip
bower ng-closure-runner#*                   EPERM EPERM, rename 'C:\Users\gimmi\AppData\Roaming\bower\cache\packages\b49378d5565266ad51701fa65c017d3e\_wildcard'

Stack trace:
Error: EPERM, rename 'C:\Users\gimmi\AppData\Roaming\bower\cache\packages\b49378d5565266ad51701fa65c017d3e\_wildcard'

Console trace:
Trace
    at StandardRenderer.error (C:\Users\gimmi\AppData\Roaming\npm\node_modules\bower\lib\renderers\StandardRenderer.js:74:17)
    at Logger.updateNotifier.packageName (C:\Users\gimmi\AppData\Roaming\npm\node_modules\bower\bin\bower:109:18)
    at Logger.EventEmitter.emit (events.js:95:17)
    at Logger.emit (C:\Users\gimmi\AppData\Roaming\npm\node_modules\bower\node_modules\bower-logger\lib\Logger.js:29:39)
    at C:\Users\gimmi\AppData\Roaming\npm\node_modules\bower\lib\commands\install.js:27:16
    at _rejected (C:\Users\gimmi\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:808:24)
    at C:\Users\gimmi\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:834:30
    at Promise.when (C:\Users\gimmi\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:1079:31)
    at Promise.promise.promiseDispatch (C:\Users\gimmi\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:752:41)
    at C:\Users\gimmi\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:574:44

System info:
Bower version: 1.2.8
Node version: 0.10.24
OS: Windows_NT 6.2.9200 x64

Most helpful comment

I agree, this is a bug with bower. The workaround is to roll back to [email protected]:

npm uninstall -g bower
npm install -g [email protected]

All 16 comments

I agree, this is a bug with bower. The workaround is to roll back to [email protected]:

npm uninstall -g bower
npm install -g [email protected]

Yes, with [email protected] it works

It doesn't work on my end with bower 1.2.6:

Running "subgrunt:angularjs" (subgrunt) task

Installed node modules in "bower_components/angularjs".
| [email protected] node_modules\karma-junit-reporter
└── [email protected]
Failed running "grunt default" in "bower_components/angularjs".
Warning:
! npm http GET https://registry.npmjs.org/xmlbuilder/0.4.2
npm http 304 https://registry.npmjs.org/xmlbuilder/0.4.2
[email protected] node_modules\karma-junit-reporter
└── [email protected]
Running "bower" task
bower: not-cached ng-closure-runner
bower: resolve ng-closure-runner
bower: not-cached closure-compiler
bower: resolve closure-compiler
bower: cached bootstrap
bower: validate bootstrap
bower: cached jquery
bower: validate jquery
bower: download ng-closure-runner
bower: download closure-compiler
bower: extract ng-closure-runner
bower: cached lunr.js
bower: validate lunr.js
bower: cached google-code-prettify
bower: validate google-code-prettify
bower: cached components-font-awesome
bower: validate components-font-awesome
bower: extract closure-compiler
Warning: EPERM, rename 'C:\Users\Brandstone\AppData\Roaming\bower\cache\packages\b49378d5565266ad51701fa65c017d3e_wildcard' Use --force to continue.

Aborted due to warnings.

Use --force to continue.

Windows 7 here - confirming that 1.2.8 doesn't work, but going back to 1.2.6 works.

@angi- ran into the issue again too, after reinstalling 1.2.6. Just deleted the bower/cache folder and it looks fine now.

image

When I install RAW I found the similar error
I check the path
'C:\Users\Conia\AppData\Roaming\bower\cache\packages\fd71ff9047cf3d1a3acf9a29600242a6'
and found it was empty so I deleted the folder ('fd71ff9047cf3d1a3acf9a29600242a6')
then reinstall RAW (by command: bower install)
It's OK for me

[email protected] works for me too

Just reinstalling or downgrading to 1.2.6 produced the same error.
updating the decompress-zip package after installing bower solved it for me :
npm update decompress-zip
After this 'bower install' proceeded without the error mentioned above.

The combination of rolling back the bower version to 1.2.6, blowing out all the application cache,and re-running did the trick for me too. Neither step worked by itself (i.e., removing the cache and re-running with the current bower version still failed).

Updating the decompress-zip solved it for me!

npm uninstall -g bower && npm update decompress-zip && npm install -g bower

@danilodeveloper you solved man !

;)
Em 30/06/2014 08:24, "Adrian Enriquez" [email protected] escreveu:

You saved the day @danilodeveloper https://github.com/danilodeveloper !

—
Reply to this email directly or view it on GitHub
https://github.com/angular/angular.js/issues/5502#issuecomment-47520561.

@danilodeveloper Unfortunately your solution doesn't work for me. Can you please tell me the name of your node version and bower? I would like to run "bower install livereload --save-dev".

@PunkSage We have now Windows CI. Feel free to add failing test if you want us to fix it.

when I run "npm install -g bower"
it shows like below
C:\UsersPrashant.shukla\AppData\Roamingnpm\bower -> C:\UsersPrashant.shukla\AppData\Roamingnpm\node_modules\bower\bin\bower
[email protected] C:\UsersPrashant.shukla\AppData\Roamingnpm\node_modules\bower

After this when I check
"bower -v"
found
bash: bower: command not found
How to fix it?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

kishanmundha picture kishanmundha  Â·  3Comments

jtorbicki picture jtorbicki  Â·  3Comments

th0r picture th0r  Â·  3Comments

WesleyKapow picture WesleyKapow  Â·  3Comments

ashclarke picture ashclarke  Â·  3Comments