framework7io
npm run serve
npm run serve don't work but with http-serve i solve..
Someone can clarify this ?
$ npm run serve
[email protected] serve /home/XXX/Project/fw7-single-page/my-app http-server ./www/ -o -c 1 -a localhost
events.js:174 throw er; // Unhandled 'error' event ^
Error: listen EADDRNOTAVAIL: address not available 10.0.24.149:8080
at Server.setupListenHandle [as _listen2] (net.js:1262:19)
at listenInCluster (net.js:1327:12)
at GetAddrInfoReqWrap.doListen [as callback] (net.js:1460:7)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:61:10)
Emitted 'error' event at:
at emitErrorNT (net.js:1306:8)
at process._tickCallback (internal/process/next_tick.js:63:19)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] serve: http-server ./www/ -o -c 1 -a localhost
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] serve script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in: npm ERR! /home/XXX/.npm/_logs/2019-09-26T08_13_37_817Z-debug.log
This's a complete log:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'serve' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'preserve', 'serve', 'postserve' ]
5 info lifecycle [email protected]~preserve: [email protected]
6 info lifecycle [email protected]~serve: [email protected]
7 verbose lifecycle [email protected]~serve: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~serve: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/XXX/Project/fw7-single-page/my-app/node_modules/.bin:/home/XXX/.local/bin:/home/XXX/bin:/home/XXX/.local/bin:/home/XXX/bin:/usr/share/Modules/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin::/home/XXX/Android/Sdk/
9 verbose lifecycle [email protected]~serve: CWD: /home/alternet.italfonso/Project/fw7-single-page/my-app
10 silly lifecycle [email protected]~serve: Args: [ '-c', 'http-server ./www/ -o -c 1 -a localhost' ]
11 silly lifecycle [email protected]~serve: Returned: code: 1 signal: null
12 info lifecycle [email protected]~serve: Failed to exec serve script
13 verbose stack Error: [email protected] serve: http-server ./www/ -o -c 1 -a localhost
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.http-server ./www/ -o -c 1 -a localhost
22 error Exit status 1
23 error Failed at the [email protected] serve script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
~
