Hi. I may be missing something really obvious but we use Middleman for a fairly large project and we’re being hit during development by it being incredibly slow when we make a change and then refresh the page locally. It didn’t used to be this noticeable. If I make a tiny change in one content html.erb file while running --verbose I can see if says there’s a change in that folder and then it runs through basically every other file in source saying ‘Possible change’ and then after that I get all the ‘running manipulator’.
Is there a way to get Middleman to not do all this. To just know which file has been changed and then not run through everything? Half the time it takes so long it’s quicker to just kill it off and restart it.
How about when you don’t use --verbose? Is the console polluted with many == LiveReloading path: … lines? Or just one that actually has been changed?