re: Setting up a React Environment for ASP.NET MVC VIEW POST

FULL DISCUSSION
 

Generally I prefer a watching build and manual refresh to browser sync. The number of times I want to lose track of an active debug state on the client as I type in an IDE are few. I've also experienced issues with synchronization and blocked calls regularly, as well as build issues that I catch much sooner if I can see the build output.

The last point is why I generally don't even bother with ide integration and just have a terminal session open persistently to run/monitor the updating build.

 

I've also experienced issues with synchronization and blocked calls regularly, as well as build issues that I catch much sooner if I can see the build output.

...

I generally don't even bother with ide integration

I can empathize with your experience because
I've also been bitten badly trying to figure out why a page wasn't working properly as I assumed the site was rendered correctly without any build issues.

That's why I have a separate build script that'd just run webpack without watching the file change so I can fire up an one off build when I am paranoid 😀😄

code of conduct - report abuse