Specifying the --port flag seems to have no effect

The --port flag seems to have no effect: $ lite-server --verbose --port=8081 options { port: 8081, openPath: ‘.’, files: [ ‘.//*.html’, './/.css’, './__/.js’ ], baseDir: ‘./’, fallback: ‘/./index.html’ } [BS] Access URLs:

---

   Local: http://localhost:3000
External: http://<my-ip>:3000

---

      UI: http://localhost:3001

UI External: http://<my-ip>:3001

---

So the console output looks as though the server is listening on ports 3000 and 3001 and netstat supports that: $ netstat -at tcp6 0 0 [::]:3000 [::]:* LISTEN
tcp6 0 0 [::]:3001 [::]:* LISTEN

Does browser-sync not support the port option properly?

[cgmartin]

@ramswaroop OK, I didn’t look closely at your file name… the contents made me think it was a .json file.

To use the bs-config.js format, just make sure to export it just like any other Node.js module:

module.export = { port: 8000 };   // quotes around field properties not required here

[Steveb-p]

@cgmartin I just slammed the same issue that others had here - my configuration file had no effect even though lite-server readme stated it was the correct way to do it. After a couple of looks into the library I realized that a new major version was out.

Would it be ok if a note were to be added to readme that this behaviour was added in 2.0.0?