Anyone having problems with running webpack with watch-poll and homestead crashing randomly after a while? I can confirm that this is not project/code specific and happens all the time.
Thanks for any suggestions.
when I run with watch on homestead (ssh/cli), it pegs my host (mac) cpu at 100+%. So, I run in on the host instead of from within the vm. It drops cpu usage down to ~8%. I'm not sure why it does that, but it was turning my macbook into a lap warmer before changing it and only running via host.
Thanks for your reaction. Does anyone have an idea why does it behave this way on vms? I don't want to mess my localhost with build stuff.
It won't mess your host with build stuff. Everything is still done in the laravel directory, which is also the homestead directory...
Well, what I meant was mainly losing control over build environment which should stay the same for whole team. (Main idea behind the homestead, right?) It opens a way for issues like.. "It's working on my localhost, but not on yours - let's spend a day to sort things out".
Please or to participate in this conversation.