Overview
If you select a component so that you can see it's prop form on the right, and then delete the component, the props form throws an error (which is caught by the Error Boundary).
Proposed resolution
When deleting a component ensure the "selectedComponent" state is unset so we don't try to render the form for a component that no longer exists.
I think it would be nice to, upon deleting a component, set the selectedComponent to be the 'next' component so that you could just repeatedly hit the delete key to delete a whole series of components one after the other.
User interface changes

Comments
Comment #2
jessebaker commentedComment #6
jessebaker commentedThanks for the speedy fix. I've raised a follow up feature request #3484570: [Needs design] Automatically select the next component on deleting a component