mean stack installation error #4898

Closed
kshatriy opened this Issue Mar 18, 2014 · 4 comments

Comments

Projects
None yet
4 participants
@kshatriy

Hello,

I was trying to install MEAN stack as per mean.io instructions (http://www.mean.io/#!/docs).Found the following error :

44029 silly gunzTarPerm extractEntry tests/ssl/test.crt
44030 silly gunzTarPerm modified mode [ 'tests/ssl/test.crt', 438, 420 ]
44031 silly gunzTarPerm extractEntry tests/ssl/test.key
44032 silly gunzTarPerm modified mode [ 'tests/ssl/test.key', 438, 420 ]
44033 silly gunzTarPerm extractEntry package.json
44034 silly gunzTarPerm modified mode [ 'package.json', 438, 420 ]
44035 error Error: ENOENT, lstat 'D:\MY WORK\RECYCLE\mean\node_modules\karma-coverage\node_modules\istanbul\test\run.js'
44036 error If you need help, you may report this *entire* log,
44036 error including the npm and node versions, at:
44036 error     <http://github.com/isaacs/npm/issues>
44037 error System Windows_NT 6.1.7601
44038 error command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
44039 error cwd D:\MY WORK\RECYCLE\mean
44040 error node -v v0.10.25
44041 error npm -v 1.3.24
44042 error path D:\MY WORK\RECYCLE\mean\node_modules\karma-coverage\node_modules\istanbul\test\run.js
44043 error fstream_path D:\MY WORK\RECYCLE\mean\node_modules\karma-coverage\node_modules\istanbul\test\run.js
44044 error fstream_type File
44045 error fstream_class FileWriter
44046 error code ENOENT
44047 error errno 34
44048 error fstream_stack C:\Program Files\nodejs\node_modules\npm\node_modules\fstream\lib\writer.js:284:26
44048 error fstream_stack Object.oncomplete (fs.js:107:15)
44049 verbose exit [ 34, true ]

Regards,

@smikes

This comment has been minimized.

Show comment Hide comment
@smikes

smikes Nov 13, 2014

Contributor

Are you still seeing this error? If so, can you please create a gist (http://gist.github.com) and attach the entire npm-debug.log file that you get from running npm install.

Thanks.

Contributor

smikes commented Nov 13, 2014

Are you still seeing this error? If so, can you please create a gist (http://gist.github.com) and attach the entire npm-debug.log file that you get from running npm install.

Thanks.

@smikes

This comment has been minimized.

Show comment Hide comment
@smikes

smikes Nov 20, 2014

Contributor

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

To update npm on Windows, follow the instructions here: https://github.com/npm/npm/wiki/Troubleshooting#upgrading-on-windows

Contributor

smikes commented Nov 20, 2014

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

To update npm on Windows, follow the instructions here: https://github.com/npm/npm/wiki/Troubleshooting#upgrading-on-windows

@smikes

This comment has been minimized.

Show comment Hide comment
@smikes

smikes Nov 23, 2014

Contributor

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 re-open it!)

Thanks!

Contributor

smikes commented Nov 23, 2014

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 re-open it!)

Thanks!

@othiym23

This comment has been minimized.

Show comment Hide comment
@othiym23

othiym23 Dec 1, 2014

Contributor

Closing as abandoned. Open a new issue if you encounter this behavior again!

Contributor

othiym23 commented Dec 1, 2014

Closing as abandoned. Open a new issue if you encounter this behavior again!

@othiym23 othiym23 closed this Dec 1, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment