Menu icon Foundation

Developer | Birmingham, UK

Head of Digital at Switch, Foundation enthusiast.

My Posts


My Comments

Jon Hurley commented on Max Audron's post almost 4 years

I have the same issue. After much messing around, I have isolated it to imagemin. Doesn't matter whether I test a build with a single PNG or JPG it falls over at the same point.
```
> [email protected] build D:\Projects\jct-corp
> gulp build --production

[16:44:40] Using gulpfile D:\Projects\jct-corp\gulpfile.js
[16:44:40] Starting 'build'...
[16:44:40] Starting 'clean'...
[16:44:40] Finished 'clean' after 19 ms
[16:44:40] Starting 'pages'...
[16:44:41] Starting 'sass'...
[16:44:42] Starting 'javascript'...
[16:44:43] Starting 'images'...
[16:44:43] Starting 'copy'...

events.js:141
throw er; // Unhandled 'error' event
^
Error: spawn D:\Projects\XXX\node_modules\gulp-imagemin\node_modules\image
min\node_modules\imagemin-jpegtran\node_modules\jpegtran-bin\vendor\jpegtran.exe
ENOENT
at exports._errnoException (util.js:856:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
at onErrorNT (internal/child_process.js:344:16)
at nextTickCallbackWith2Args (node.js:478:9)
at process._tickCallback (node.js:392:17)
Error: [email protected] build: gulp build --production
Exit status 1
at EventEmitter. (C:\Users\JMH\AppData\Roaming\npm\
node_modules\foundation-cli\node_modules\npm\lib\utils\lifecycle.js:214:16)
at emitTwo (events.js:87:13)
at EventEmitter.emit (events.js:172:7)
at ChildProcess. (C:\Users\JMH\AppData\Roaming\npm\
node_modules\foundation-cli\node_modules\npm\lib\utils\spawn.js:24:14)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at maybeClose (internal/child_process.js:821:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
```

Jon Hurley commented on Jon Hurley's post almost 4 years

I'm not using CLI, I followed the instructions for the Zurb template from here...

http://foundation.zurb.com/sites/docs/starter-projects.html

Download and unzip the master template files into a project directory.

npm install
bower install
npm start

I have a colleague with an install that is working.

I can hack mine to work (by removing the img reference in line 23 of the standard gulpfile) but fundamentally it is not recognising the creation or changes to any files in the img foider, and the images watch function does not run.

Posts Followed


Following

    No Content

Followers

My Posts

My Comments

You commented on Max Audron's post almost 4 years

I have the same issue. After much messing around, I have isolated it to imagemin. Doesn't matter whether I test a build with a single PNG or JPG it falls over at the same point.
```
> [email protected] build D:\Projects\jct-corp
> gulp build --production

[16:44:40] Using gulpfile D:\Projects\jct-corp\gulpfile.js
[16:44:40] Starting 'build'...
[16:44:40] Starting 'clean'...
[16:44:40] Finished 'clean' after 19 ms
[16:44:40] Starting 'pages'...
[16:44:41] Starting 'sass'...
[16:44:42] Starting 'javascript'...
[16:44:43] Starting 'images'...
[16:44:43] Starting 'copy'...

events.js:141
throw er; // Unhandled 'error' event
^
Error: spawn D:\Projects\XXX\node_modules\gulp-imagemin\node_modules\image
min\node_modules\imagemin-jpegtran\node_modules\jpegtran-bin\vendor\jpegtran.exe
ENOENT
at exports._errnoException (util.js:856:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
at onErrorNT (internal/child_process.js:344:16)
at nextTickCallbackWith2Args (node.js:478:9)
at process._tickCallback (node.js:392:17)
Error: [email protected] build: gulp build --production
Exit status 1
at EventEmitter. (C:\Users\JMH\AppData\Roaming\npm\
node_modules\foundation-cli\node_modules\npm\lib\utils\lifecycle.js:214:16)
at emitTwo (events.js:87:13)
at EventEmitter.emit (events.js:172:7)
at ChildProcess. (C:\Users\JMH\AppData\Roaming\npm\
node_modules\foundation-cli\node_modules\npm\lib\utils\spawn.js:24:14)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at maybeClose (internal/child_process.js:821:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
```

You commented on Jon Hurley's post almost 4 years

I'm not using CLI, I followed the instructions for the Zurb template from here...

http://foundation.zurb.com/sites/docs/starter-projects.html

Download and unzip the master template files into a project directory.

npm install
bower install
npm start

I have a colleague with an install that is working.

I can hack mine to work (by removing the img reference in line 23 of the standard gulpfile) but fundamentally it is not recognising the creation or changes to any files in the img foider, and the images watch function does not run.

Posts Followed

Following

  • No Content

Followers

  • No Content