node-terminal icon indicating copy to clipboard operation
node-terminal copied to clipboard

Install , doesn't

Open lhirlimann opened this issue 7 years ago • 0 comments

[ludovic@tor1 noia-node-terminal]$ npm start

[email protected] start /home/ludovic/noia/noia-node-terminal node index

module.js:478 throw err; ^

Error: Cannot find module 'noia-protocol' at Function.Module._resolveFilename (module.js:476:15) at Function.Module._load (module.js:424:25) at Module.require (module.js:504:17) at require (internal/module.js:20:19) at Object. (/home/ludovic/noia/noia-node-terminal/node_modules/noia-node/dist/lib/master.js:6:14) at Module._compile (module.js:577:32) at Object.Module._extensions..js (module.js:586:10) at Module.load (module.js:494:32) at tryModuleLoad (module.js:453:12) at Function.Module._load (module.js:445:3)

npm ERR! Linux 4.4.96-mainline-rev1 npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "start" npm ERR! node v6.14.2 npm ERR! npm v3.10.10 npm ERR! code ELIFECYCLE npm ERR! [email protected] start: node index npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] start script 'node index'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the node-terminal package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node index npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs node-terminal npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls node-terminal npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request: npm ERR! /home/ludovic/noia/noia-node-terminal/npm-debug.log

Runing on fedora server on aarch64

The log contains the following: [ludovic@tor1 noia-node-terminal]$ cat npm-debug.log 0 info it worked if it ends with ok 1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ] 2 info using [email protected] 3 info using [email protected] 4 verbose run-script [ 'prestart', 'start', 'poststart' ] 5 info lifecycle [email protected]~prestart: [email protected] 6 silly lifecycle [email protected]~prestart: no script for prestart, continuing 7 info lifecycle [email protected]~start: [email protected] 8 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true 9 verbose lifecycle [email protected]~start: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/ludovic/noia/noia-node-terminal/node_modules/.bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/ludovic/.local/bin:/home/ludovic/bin 10 verbose lifecycle [email protected]~start: CWD: /home/ludovic/noia/noia-node-terminal 11 silly lifecycle [email protected]~start: Args: [ '-c', 'node index' ] 12 silly lifecycle [email protected]~start: Returned: code: 1 signal: null 13 info lifecycle [email protected]~start: Failed to exec start script 14 verbose stack Error: [email protected] start: node index 14 verbose stack Exit status 1 14 verbose stack at EventEmitter. (/usr/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/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:920:16) 14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:230:5) 15 verbose pkgid [email protected] 16 verbose cwd /home/ludovic/noia/noia-node-terminal 17 error Linux 4.4.96-mainline-rev1 18 error argv "/usr/bin/node" "/usr/bin/npm" "start" 19 error node v6.14.2 20 error npm v3.10.10 21 error code ELIFECYCLE 22 error [email protected] start: node index 22 error Exit status 1 23 error Failed at the [email protected] start script 'node index'. 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 node-terminal package, 23 error not with npm itself. 23 error Tell the author that this fails on your system: 23 error node index 23 error You can get information on how to open an issue for this project with: 23 error npm bugs node-terminal 23 error Or if that isn't available, you can get their info via: 23 error npm owner ls node-terminal 23 error There is likely additional logging output above. 24 verbose exit [ 1, true ] [ludovic@tor1 noia-node-terminal]$

lhirlimann avatar Jun 21 '18 17:06 lhirlimann