Trouble installing bower on Windows 8.1 #5736

githubpushp opened this Issue Jul 20, 2014 · 2 comments


None yet

3 participants

Below is the last part of log file with errors -

6938 error Error: ENOENT, chmod 'C:\Users\pushpendra.singh\AppData\Roaming\npm\node_modules\bower\node_modules\inquirer\node_modules\through\readme.markdown'
6939 error If you need help, you may report this *entire* log,
6939 error including the npm and node versions, at:
6939 error     <>
6940 error System Windows_NT 6.2.9200
6941 error command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "bower"
6942 error cwd C:\Users\pushpendra.singh
6943 error node -v v0.10.29
6944 error npm -v 1.4.14
6945 error path C:\Users\pushpendra.singh\AppData\Roaming\npm\node_modules\bower\node_modules\inquirer\node_modules\through\readme.markdown
6946 error fstream_path C:\Users\pushpendra.singh\AppData\Roaming\npm\node_modules\bower\node_modules\inquirer\node_modules\through\readme.markdown
6947 error fstream_type File
6948 error fstream_class FileWriter
6949 error fstream_finish_call chmod
6950 error code ENOENT
6951 error errno 34
6952 error fstream_stack C:\Program Files\nodejs\node_modules\npm\node_modules\fstream\lib\writer.js:305:19
6952 error fstream_stack Object.oncomplete (fs.js:107:15)
6953 verbose exit [ 34, true ]

There are other errors with readme for various modules, like the one below -

36 silly resolved     _resolved: '',
36 silly resolved     readme: 'ERROR: No README data found!' } ]
@othiym23 othiym23 added the windows label Jul 20, 2014
smikes commented Dec 27, 2014

Is this still a problem for you?

This looks like the sort of race condition that used to happen with older versions of npm.

There have been a lot of improvements to npm -- especially around conflicts and race conditions during install -- since 1.4.14. Can you try updating your npm installation?

To update npm on Windows, follow the instructions here:

We are trying to clean up older npm issues, so if we don't hear back from you within a week, we will close this issue. (Don't worry -- you can always come back again and open a new issue!)



Closing as abandoned.

@othiym23 othiym23 closed this Feb 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment