change default port about live-server HOT 6 CLOSED

Hey @abhishekisnot @famousgarkin, someone else submitted a PR that would make live-server automatically choose a new port when the current port is in use (PR #12).

I've cleaned it up and included it within my larger PR #48. This means when you call live-server without --port, it'll try port 8080, and then randomly choose an open port > 5000. Does this fit your needs?

I understand --port=9000 will do the job, but I don't like to fire long command every time :)
-- @abhishekisnot

I feel you there :).

Here's a quick side tip: make use of the "scripts" key within your package.json (see npm docs).

1. First, add live-server as a local dev dependency to your project. This ensures you'll always have the tool frozen and stable for your project:

   $ npm install live-server --save-dev

2. Then, add the following to your package.json:

   {
     // ... package.json metdata ...
     "scripts": {
       "server" : "./node_modules/.bin/live-server --port=9000"
     }
   }

   You can also add other options, e.g., --no-browser, etc. To run the script, it's just:

   npm run-script server

from live-server.

Thank you very much for auto pick next available port change.

I know the npm scripts facility. I always use that for most project once poc is mature enough to share.

Default port can be setup in various ways anyways, for example: I have zsh alias setup for live-server to pick 9000, so this issue is not high impact.

Just that I was surprised to see we pickup 8080 by default where as most dev servers would choose 9000 or 5000 (browser sync for example)

BTW, we don't need full path in npm scripts, .bin is in path anyways for all npm scripts.

from live-server.

BTW, we don't need full path in npm scripts, .bin is in path anyways for all npm scripts.

I guess you learn something new everyday, haha. Thanks!

Just that I was surprised to see we pickup 8080 by default where as most dev servers would choose 9000 or 5000 (browser sync for example)

I think the original choice was just plain convenience. 8080 made it clear that the service is HTTP. Also, with the new auto-reconfigure-port, I guess this is now less of an issue.

Default port can be setup in various ways anyways, for example: I have zsh alias setup for live-server to pick 9000, so this issue is not high impact.

There's also an outstanding PR #33 that discusses defining per-project and per-user-global default settings. I know it's not exactly what you meant on this issue ticket, but could you let us know your thoughts there? Would you find it useful?

from live-server.

If I run this code, it will just start with port 8080.
"scripts": {
"serve": "live-server .",
"start": "live-server --port=8000"
}

Someone an idea why? Seems to be a bug or I am wrong?

from live-server.

@bes1002t try changing the command in start as:

live-server -p 8000

from live-server.

I have achieved like this (on windows):

"scripts": {
"start": "set PORT=8000 && live-server"
}

from live-server.