|
| 1 | +0 info it worked if it ends with ok |
| 2 | +1 verbose cli [ '/Users/r2fresh/.nvm/versions/v4.5.0/bin/node', |
| 3 | +1 verbose cli '/Users/r2fresh/.nvm/versions/v4.5.0/bin/npm', |
| 4 | +1 verbose cli 'start' ] |
| 5 | + |
| 6 | + |
| 7 | +4 verbose run-script [ 'prestart', 'start', 'poststart' ] |
| 8 | + |
| 9 | + |
| 10 | +7 verbose unsafe-perm in lifecycle true |
| 11 | +8 info [email protected] Failed to exec start script |
| 12 | +9 verbose stack Error: [email protected] start: `webpack-dev-server --inline --content-base .` |
| 13 | +9 verbose stack spawn ENOENT |
| 14 | +9 verbose stack at ChildProcess.<anonymous> (/Users/r2fresh/.nvm/versions/v4.5.0/lib/node_modules/npm/lib/utils/spawn.js:17:16) |
| 15 | +9 verbose stack at emitTwo (events.js:87:13) |
| 16 | +9 verbose stack at ChildProcess.emit (events.js:172:7) |
| 17 | +9 verbose stack at maybeClose (internal/child_process.js:829:16) |
| 18 | +9 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5) |
| 19 | +10 verbose pkgid [email protected] |
| 20 | +11 verbose cwd /Users/r2fresh/workspace/react-router-tutorial/lessons/01-setting-up |
| 21 | +12 error Darwin 15.6.0 |
| 22 | +13 error argv "/Users/r2fresh/.nvm/versions/v4.5.0/bin/node" "/Users/r2fresh/.nvm/versions/v4.5.0/bin/npm" "start" |
| 23 | +14 error node v4.5.0 |
| 24 | +15 error npm v2.15.9 |
| 25 | +16 error file sh |
| 26 | +17 error code ELIFECYCLE |
| 27 | +18 error errno ENOENT |
| 28 | +19 error syscall spawn |
| 29 | +20 error [email protected] start: `webpack-dev-server --inline --content-base .` |
| 30 | +20 error spawn ENOENT |
| 31 | +21 error Failed at the [email protected] start script 'webpack-dev-server --inline --content-base .'. |
| 32 | +21 error This is most likely a problem with the tutorial package, |
| 33 | +21 error not with npm itself. |
| 34 | +21 error Tell the author that this fails on your system: |
| 35 | +21 error webpack-dev-server --inline --content-base . |
| 36 | +21 error You can get information on how to open an issue for this project with: |
| 37 | +21 error npm bugs tutorial |
| 38 | +21 error Or if that isn't available, you can get their info via: |
| 39 | +21 error |
| 40 | +21 error npm owner ls tutorial |
| 41 | +21 error There is likely additional logging output above. |
| 42 | +22 verbose exit [ 1, true ] |
0 commit comments