Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- 0 info it worked if it ends with ok
- 1 verbose cli [ 'D:\\Program Files\\nodejs\\node.exe',
- 1 verbose cli 'D:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
- 1 verbose cli 'run',
- 1 verbose cli 'dev' ]
- 2 info using npm@3.10.9
- 3 info using node@v6.9.2
- 4 verbose run-script [ 'predev', 'dev', 'postdev' ]
- 5 info lifecycle @~predev: @
- 6 silly lifecycle @~predev: no script for predev, continuing
- 7 info lifecycle @~dev: @
- 8 verbose lifecycle @~dev: unsafe-perm in lifecycle true
- 9 verbose lifecycle @~dev: PATH: D:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;D:\xampp\htdocs\josh001\node_modules\.bin;C:\Program Files (x86)\Python35-32\Scripts\;C:\Program Files (x86)\Python35-32\;C:\Windows\system32;C:\Windows;C:\Windows\system32\wbem;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Intel\iCLS Client;C:\Program Files\Intel\iCLS Client;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;D:\Program Files (x86)\Skype\Phone;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files\Microsoft Network Monitor 3\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;D:\xampp\php;C:\ProgramData\ComposerSetup\bin;D:\Program Files (x86)\Skype\Phone\;C:\Program Files (x86)\GtkSharp\2.12\bin;d:\Program Files\Git\cmd;D:\Program Files\PostgreSQL\pg95\bin;C:\Program Files\PostgreSQL\pg95\bin;D:\Program Files\nodejs\;C:\Users\yearzero\AppData\Roaming\npm
- 10 verbose lifecycle @~dev: CWD: D:\xampp\htdocs\josh001
- 11 silly lifecycle @~dev: Args: [ '/d /s /c', 'gulp watch' ]
- 12 silly lifecycle @~dev: Returned: code: 3 signal: null
- 13 info lifecycle @~dev: Failed to exec dev script
- 14 verbose stack Error: @ dev: `gulp watch`
- 14 verbose stack Exit status 3
- 14 verbose stack at EventEmitter.<anonymous> (D:\Program Files\nodejs\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.<anonymous> (D:\Program Files\nodejs\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 @
- 16 verbose cwd D:\xampp\htdocs\josh001
- 17 error Windows_NT 6.1.7601
- 18 error argv "D:\\Program Files\\nodejs\\node.exe" "D:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "dev"
- 19 error node v6.9.2
- 20 error npm v3.10.9
- 21 error code ELIFECYCLE
- 22 error @ dev: `gulp watch`
- 22 error Exit status 3
- 23 error Failed at the @ dev script 'gulp watch'.
- 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 package,
- 23 error not with npm itself.
- 23 error Tell the author that this fails on your system:
- 23 error gulp watch
- 23 error You can get information on how to open an issue for this project with:
- 23 error npm bugs
- 23 error Or if that isn't available, you can get their info via:
- 23 error npm owner ls
- 23 error There is likely additional logging output above.
- 24 verbose exit [ 1, true ]
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement