Bower hangs when installing Ubuntu dependencies

I am trying to install many dependencies using Bower on Ubuntu 14.04. Installation hangs at a semi-random point (one of jQuery, closure-library, or closure compiler). Versions below, along with bower.json (anonymous).

Node v0.10.35
NPM v1.4.28
Bower v1.3.12

bower.json

{
  "name": "redacted",
  "version": "0.12.2",
  "homepage": "redacted",
  "description": "redacted",
  "private": true,
  "ignore": [
    "**/.*",
    "node_modules",
    "bower_components"
  ],
  "dependencies": {
    "angular": "~1.3.0",
    "angular-ui-router": "~0.2.10",
    "angular-cookie": "~4.0.6",
    "bootstrap": "~3.2.0",
    "angular-animate": "~1.3.0",
    "signalr": "*",
    "angular-translate": "~2.4.0",
    "fallback": "https://github.com/dolox/fallback.git#v2",
    "angularjs-scroll-glue": "~0.0.1",
    "angular-swfobject": "~1.0.2",
    "swfobject": "*",
    "angular-moment": "~0.8.3",
    "momentjs": "~2.8.3",
    "moment-timezone": "~0.2.2",
    "angular-uuid4": "~0.2.0",
    "font-awesome": "~4.2.0",
    "angular-strap": "~2.1.4",
    "angular-motion": "~0.3.4",
    "angularjs-toaster": "~0.4.9",
    "angular-hotkeys": "https://github.com/chieffancypants/angular-hotkeys.git#1.4.5"
  },
  "devDependencies": {
    "es5-shim": "~4.0.3",
    "closure-compiler": "~0.2.6",
    "closurelibrary": "*",
    "closure-library-externs": "git@github.com:google/closure-compiler.git#v20140814",
    "angular-mocks": "~1.3.0"
  },
  "resolutions": {
    "angular": "~1.3.0"
  }
}

      

Can anyone find something wrong with bower.json

or know about any incompatibilities between bower and Ubuntu with these versions?

An example of a line from bower install

is displayed at the point where it is hanging (as mentioned, the exact point it is hanging from changes every time, although it most often happens at resolved

).

bower fallback#v2 resolved https://github.com/dolox/fallback.git#0568407bc2

+3


source to share


1 answer


Without npm-debug.log

I can't diagnose this unequivocally, but it definitely looks like some of the install / race bugs that used to propagate to earlier versions of npm - up to 2.1.

There have been many improvements to npm - especially around conflicts and race conditions during installation - since 1.4.28. Can you try updating your npm installation?



To update npm, run npm -g install npm@latest

For some Linux distributions (Debian / Ubuntu and RedHat / CentOS), the latest node version provided by the distribution may lag behind the stable version. Below are instructions from NodeSource about getting the last node.

0


source







All Articles