Since I’m seeing it happen regularly, please let me know if you’d like me to do any more specific testing. E.g. updating a plugin with a .git directory or node_modules directory and tons of little files vs one without. Updating/adding specific known plugins with just a few files (not thinking of good examples of this, but I’m sure there are some) vs some commonly-used large ones, like ACF or Gravity Forms.
If you’d like logs, I can do that, too; just give me some specific actions to take, if you’re needing to see more from my end.
Thanks for the feedback! I’ve got something on the radar for the Local team. It looks like it could be a little tricky, but they should be able to get to it in the next couple sprints, so be on the lookout for a fix!
This didn’t cause any crashes for me, but it was funny watching Instant Reload try to refresh the plugin update page – it kept asking me if I wanted to “leave the page”.
Can you try downloading the latest version of Local and let me know if it’s fixed for you?
Beautiful! Thanks so much, Ben! I usually do updates in local via CLI, and when I do them there, it bumps me briefly over to maintenance mode (the autoreload), but doesn’t error out or require a restart. Seems completely fixed!
Thanks so much – the performance improvements in the last few versions of Local for me (as I have like 50 sites installed) are dramatic. Night and day difference – absolutely loving it.
