npm start wants bundle.js on port 3000, while website started on first free port

[svdoever]

Node version: 6.2.1

npm version: 3.9.3

Operating system: OSX

Command line used: npm start

Steps to reproduce: npm start seems to do everything, but when site starts up gives error in browser console window **Failed to load resource: the server responded with a status of 404 (Not Found) http://localhost:3000/bundle.js, but the site started at port 3004! Seems like link to bundle.js is hard-coded on port 3000, while site starts up on next free port. I had another programming running that took up port 3000...

[coryhouse]

You can change the port by updating srcServer.js, distServer.js, and webpack.config.dev.js.

I haven't found a way to run at a dynamic port, but would love to see a pull request that handles it.

[svdoever]

Hi Cory, no problem... now I know I have to kill other apps taking port 3000. Might be good to take a completely different port i.e. 3918 or something like that, because most apps take port 3000:-)

By the way: my compliments on your course on PluralSight!

[coryhouse]

Resolved with 092151e