Angel Rodriguez

I think I fixed the issue.. I added the NamedModulesPlugin to the webpack.server-config.js file to correct the issue. ` plugins: [ new webpack.HotModuleReplacementPlugin(), new webpack.NamedModulesPlugin(), ],` It also shows you...

Justin it depends on the version webpack you have installed in your package.json file. Vasan is using webpack 1. were you able to resolve your issue?

Hey thanks! I'll try them. I was going to attempt to update to Router v4 once I was done with the project as a refactoring job.

Hey your welcome Vasan. Thanks for taking the time to write the book. It's great so far! 🙌🏼 Angel Sent from my iPhone > On Jun 22, 2017, at 12:59...

hey nice man! cheers! which version webpack-dev-server are you using? 2.5.1?

did you get the page up at least or is it blank? I thought you solve it already! lol > On Jul 13, 2017, at 3:43 PM, Robbie Prevost wrote:...

oh okay got it. try to change something on the client code it should refresh right?

exactly, but you at least got the same screen on both ports right?

yeah but should be taken care of in your webpack.config.js file right?

awesome! Yeah you're right I guessing because all the client side code is actually done in .jsx.