-
Notifications
You must be signed in to change notification settings - Fork 27
Open
Description
I am trying to start spike watch on a different port. I tried -p, --port, as per manual, unfortunately, the port setting is ignored.
~/git/test/test$ spike watch -p 3003
compiled (0.496s)
node:events:491
throw er; // Unhandled 'error' event
^
Error: listen EADDRINUSE: address already in use :::3001
at Server.setupListenHandle [as _listen2] (node:net:1469:16)
at listenInCluster (node:net:1517:12)
at Server.listen (node:net:1605:7)
at Object.startServer [as fn] (/home/piotr/git/test/test/node_modules/browser-sync-ui/lib/async.js:123:39)
at /home/piotr/git/test/test/node_modules/browser-sync-ui/lib/UI.js:184:14
at iterate (/home/piotr/git/test/test/node_modules/async-each-series/index.js:8:5)
at /home/piotr/git/test/test/node_modules/async-each-series/index.js:16:16
at /home/piotr/git/test/test/node_modules/browser-sync-ui/lib/UI.js:192:13
at Object.setUrlOptions [as fn] (/home/piotr/git/test/test/node_modules/browser-sync-ui/lib/async.js:76:9)
at /home/piotr/git/test/test/node_modules/browser-sync-ui/lib/UI.js:184:14
Emitted 'error' event on Server instance at:
at emitErrorNT (node:net:1496:8)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
code: 'EADDRINUSE',
errno: -98,
syscall: 'listen',
address: '::',
port: 3001
}
- Expected behavior:
spike watchstarts on port 3003 - Actual behavior:
spike watchstarts on port 3001.
Metadata
Metadata
Assignees
Labels
No labels