You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 16, 2019. It is now read-only.
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'build' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle [email protected]prebuild: [email protected]
6 silly lifecycle [email protected]prebuild: no script for prebuild, continuing
7 info lifecycle [email protected]build: [email protected]
8 verbose lifecycle [email protected]build: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]build: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Applications/MAMP/htdocs/iwv/wp-content/themes/FoundationPress/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/kamov/phalcontools
10 verbose lifecycle [email protected]build: CWD: /Applications/MAMP/htdocs/iwv/wp-content/themes/FoundationPress
11 silly lifecycle [email protected]build: Args: [ '-c', 'gulp build' ]
12 silly lifecycle [email protected]build: Returned: code: 1 signal: null
13 info lifecycle [email protected]~build: Failed to exec build script
14 verbose stack Error: [email protected] build: gulp build
14 verbose stack Exit status 1
14 verbose stack at EventEmitter. (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:191:7)
14 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:191:7)
14 verbose stack at maybeClose (internal/child_process.js:877:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid [email protected]
16 verbose cwd /Applications/MAMP/htdocs/iwv/wp-content/themes/FoundationPress
17 error Darwin 14.5.0
18 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
19 error node v6.9.1
20 error npm v3.10.8
21 error code ELIFECYCLE
22 error [email protected] build: gulp build
22 error Exit status 1
23 error Failed at the [email protected] build script 'gulp build'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the foundationpress package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error gulp build
23 error You can get information on how to open an issue for this project with:
23 error npm bugs foundationpress
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls foundationpress
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
The text was updated successfully, but these errors were encountered:
@kamov : Can you please try deleting your node_modules folder, then run npm install and paste see if you get any errors on install? I'm running on the same version of node and npm as you (on a mac), and I get no errors at all on a fresh install.
When I run "npm run build" I get below error:
from debug file:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'build' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle [email protected]
prebuild: [email protected]prebuild: no script for prebuild, continuing6 silly lifecycle [email protected]
7 info lifecycle [email protected]
build: [email protected]build: unsafe-perm in lifecycle true8 verbose lifecycle [email protected]
9 verbose lifecycle [email protected]
build: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Applications/MAMP/htdocs/iwv/wp-content/themes/FoundationPress/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/kamov/phalcontoolsbuild: CWD: /Applications/MAMP/htdocs/iwv/wp-content/themes/FoundationPress10 verbose lifecycle [email protected]
11 silly lifecycle [email protected]
build: Args: [ '-c', 'gulp build' ]build: Returned: code: 1 signal: null12 silly lifecycle [email protected]
13 info lifecycle [email protected]~build: Failed to exec build script
14 verbose stack Error: [email protected] build:
gulp build
14 verbose stack Exit status 1
14 verbose stack at EventEmitter. (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:191:7)
14 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:191:7)
14 verbose stack at maybeClose (internal/child_process.js:877:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid [email protected]
16 verbose cwd /Applications/MAMP/htdocs/iwv/wp-content/themes/FoundationPress
17 error Darwin 14.5.0
18 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
19 error node v6.9.1
20 error npm v3.10.8
21 error code ELIFECYCLE
22 error [email protected] build:
gulp build
22 error Exit status 1
23 error Failed at the [email protected] build script 'gulp build'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the foundationpress package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error gulp build
23 error You can get information on how to open an issue for this project with:
23 error npm bugs foundationpress
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls foundationpress
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
The text was updated successfully, but these errors were encountered: