Reputation: 7682
I am have been attempting to install bower repeatedly for days. The install hang at the same point -
npm verb about to build C:\Users\spjbd\AppData\Roaming\npm\node_modules\bower\no
de_modules\insight
npm info build C:\Users\spjbd\AppData\Roaming\npm\node_modules\bower\node_module
s\insight
npm verb linkStuff [ true,
npm verb linkStuff 'C:\\Users\\spjbd\\AppData\\Roaming\\npm\\node_modules',
npm verb linkStuff false,
npm verb linkStuff 'C:\\Users\\spjbd\\AppData\\Roaming\\npm\\node_modules\\bow
er\\node_modules' ]
npm info linkStuff [email protected]
npm verb linkBins [email protected]
npm verb linkMans [email protected]
npm verb rebuildBundles [email protected]
npm verb rebuildBundles [ '.bin',
npm verb rebuildBundles 'async',
npm verb rebuildBundles 'chalk',
npm verb rebuildBundles 'configstore',
npm verb rebuildBundles 'inquirer',
npm verb rebuildBundles 'lodash.debounce',
npm verb rebuildBundles 'object-assign',
npm verb rebuildBundles 'os-name',
npm verb rebuildBundles 'tough-cookie' ]
npm info install [email protected]
npm info postinstall [email protected]
npm verb unlock done using C:\Users\spjbd\AppData\Roaming\npm-cache\_locks\insig
ht-46285e0bf21e5a96.lock for C:\Users\spjbd\AppData\Roaming\npm\node_modules\bow
er\node_modules\insight
I have tried several different methods to counteract -
An additional error that has come up is that the build has had issues with the npm-cache directory.
Any insight to getting bower running correctly?
Upvotes: 2
Views: 562
Reputation: 4098
I'm using Windows 10 and I had similar issue. Instead of using Windows command prompt for npm install -g bower
, I used git bash command prompt. It worked.
Upvotes: 1
Reputation: 11
Setting the registry helped me for hanging installs. Simply run
npm config set registry https://registry.npmjs.org/
You may need to use sudo to alter your config file though.
Upvotes: 1
Reputation: 10818
Are you trying this with [email protected]
? If so, can you try with [email protected]
, which is a known-good version?
Upvotes: 2