Closed dwittner closed 9 years ago
Starting buster-server twice produces the following output for me on my windows machine:
buster-server
Address already in use. Pick another port with -p/--port to start buster-server buster-server running on http://localhost:1111
The second message isn't displayed on my linux machine. I don't know whether it is the OS or node.js version which makes the different.
I have seen that we use process.nextTick() in buster-server-cli\lib\server-cli.js. I think using a callback for server.listen instead, would be better and solve this problem.
process.nextTick()
Please take a look at the PR.
Fixed in version 0.3.2 of buster-server-cli.
Starting
buster-server
twice produces the following output for me on my windows machine:The second message isn't displayed on my linux machine. I don't know whether it is the OS or node.js version which makes the different.
I have seen that we use
process.nextTick()
in buster-server-cli\lib\server-cli.js. I think using a callback for server.listen instead, would be better and solve this problem.