ENOENT error while running the generator

[BeOleg]

browser-sync@0.9.1 node_modules/browser-sync
├── path@0.4.9
├── commander@2.1.0
├── opn@0.1.2
├── dev-ip@0.1.7
├── browser-sync-client@0.1.9
├── ua-parser-js@0.6.2
├── optimist@0.6.1 (wordwrap@0.0.2, minimist@0.0.10)
├── http-proxy@1.0.3 (eventemitter3@0.1.2)
├── lodash@2.2.1
├── resp-modifier@0.0.4
├── cl-strings@0.0.5 (chalk@0.4.0, lodash@2.4.1)
├── gaze@0.5.1 (globule@0.1.0)
├── browser-sync-control-panel@0.0.5 (through@2.3.4)
├── portscanner-plus@0.1.0 (q@1.0.1, portscanner@0.2.3)
├── socket.io@0.8.7 (policyfile@0.0.4, redis@0.6.7, socket.io-client@0.8.7)
├── connect@2.13.1 (uid2@0.0.3, methods@0.1.0, cookie-signature@1.0.1, pause@0.0.1, debug@0.8.1, fresh@0.2.0, qs@0.6.6, bytes@0.2.1, buffer-crc32@0.2.1, raw-body@1.1.3, batch@0.5.0, cookie@0.1.0, compressible@1.0.0, negotiator@0.3.0, send@0.1.4, multiparty@2.2.0)
└── url@0.7.9 (querystring@0.1.0, punycode@1.0.0)
execvp(): No such file or directory

events.js:72
throw er; // Unhandled 'error' event
^
Error: spawn ENOENT
at errnoException (child_process.js:988:11)
at Process.ChildProcess._handle.onexit (child_process.js:779:34)

Any suggestions?

Thanks in advance :)

[Swiip]

Hi,

I don't succeed to reproduce your problem, can you give more information ? When do you get the error, after answering the questions ?

If you are on windows, perhaps it's only npm which are failing (it appens), try to re-run npm install. It could be enough.

I can use also other info like : os, version of the generator, answers in the generator...

Matthieu

[mech-tools]

Hello,

Have the same issue.

browser-sync@0.9.1 node_modules/browser-sync
├── path@0.4.9
├── commander@2.1.0
├── opn@0.1.2
├── dev-ip@0.1.7
├── browser-sync-client@0.1.9
├── ua-parser-js@0.6.2
├── optimist@0.6.1 (wordwrap@0.0.2, minimist@0.0.10)
├── portscanner-plus@0.1.0 (q@1.0.1, portscanner@0.2.3)
├── http-proxy@1.0.3 (eventemitter3@0.1.2)
├── lodash@2.2.1
├── resp-modifier@0.0.4
├── cl-strings@0.0.5 (chalk@0.4.0, lodash@2.4.1)
├── gaze@0.5.1 (globule@0.1.0)
├── browser-sync-control-panel@0.0.5 (through@2.3.4)
├── socket.io@0.8.7 (policyfile@0.0.4, redis@0.6.7, socket.io-client@0.8.7)
├── connect@2.13.1 (uid2@0.0.3, methods@0.1.0, debug@0.8.1, cookie-signature@1.0.1, pause@0.0.1, fresh@0.2.0, qs@0.6.6, bytes@0.2.1, buffer-crc32@0.2.1, raw-body@1.1.3, batch@0.5.0, cookie@0.1.0, compressible@1.0.0, negotiator@0.3.0, send@0.1.4, multiparty@2.2.0)
└── url@0.7.9 (querystring@0.1.0, punycode@1.0.0)
gulp-imagemin@0.5.1 node_modules/gulp-imagemin
├── object-assign@0.3.1
├── pretty-bytes@0.1.1
├── chalk@0.4.0 (ansi-styles@1.0.0, strip-ansi@0.1.1, has-color@0.1.7)
├── gulp-util@2.2.17 (lodash._reinterpolate@2.4.1, dateformat@1.0.8-1.2.3, minimist@0.1.0, lodash.template@2.4.1, multipipe@0.1.1, vinyl@0.2.3)
├── through2@0.4.2 (xtend@2.1.2, readable-stream@1.0.27-1)
└── imagemin@0.4.6 (get-stdin@0.1.0, stat-mode@0.2.0, ware@0.2.1, rimraf@2.2.8, image-type@0.1.4, nopt@2.2.1, tempfile@0.1.3, fs-extra@0.8.1, imagemin-svgo@0.1.0, imagemin-optipng@0.1.0, imagemin-gifsicle@0.1.1, imagemin-pngquant@0.1.2, imagemin-jpegtran@0.1.0)
execvp(): No such file or directory
     _-----_
    |       |    .---------------------------------------.
    |--(o)--|    |        Bye from us! Chat soon.        |
   `---------´   |                                       |
    ( _´U`_ )    |            The Yeoman Team            |
    /___A___\    | https://github.com/yeoman/yeoman#team |
     |  ~  |     '---------------------------------------'
   __'.___.'__
 ´   `  |° ´ Y `
events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: spawn ENOENT
    at errnoException (child_process.js:988:11)
    at Process.ChildProcess._handle.onexit (child_process.js:779:34)

Happens after answering the questions.

[Swiip]

After tried to update and reinstall all my node js modules, I finally found the problem.

As a last operation, the generator use a gulp task and assume gulp is installed with "-g".

It's neither documented nor unavoidable so it's really a bug.

As a workaround you can simply type npm install -g gulp and gulp wiredep or restart the generator. But I keep the issue open until I provide a real fix.

Thanks for the report.

[Swiip]

I've added the gulp installation in the usage section. I think it will be enough.