In this [issue](https://github.com/facebook/react/issues/23373), when you navigate to [this app](https://next-rsc-notes.vercel.app/note/1646289027680) and inspect the sidebar in the components tab, you will get this error:

![image](https://user-images.githubusercontent.com/2735514/158241727-64eba8f9-5ac2-4aa7-bffa-ff9b3174a261.png)

 This is a user error. One of the components in the user's app thrown. However, the UI for this is confusing, because it seems like it's a DevTools error. We've gotten a lot of bug reports like this, and it would be good to differentiate between DevTools bugs and bugs in the app. For this task:

- [ ] Build the React DevTools extension locally (instructions [here](https://github.com/facebook/react/tree/main/packages/react-devtools-extensions)) and reproduce the error
- [ ] Figure out a way to have the front end be able to differentiate whether the error is a error within DevTools or within the user's app
- [ ] Design/implement a better UI to help app developers distinguish between these two cases
.spyOn(console, 'warn')
        .mockImplementation(() => {});
      // now force error state on <Example />
      await toggleError(true);
      consoleErrorMock.mockRestore();
      consoleWarnMock.mockRestore();
      // we are in error state now, <Example /> won't show up
      withEr
        expect(store.getElementIDAtIndex(1)).toBe(null);
      });
      // Inpsect <ErrorBoundary /> to toggle off the error state
      inspectedElement = await inspect(0);
      ement.canToggleError).toBe(true);
      ement.isErrored).toBe(true);
      // its error boundary ID is itself because it's caught the error
      
        targetErrorBoundaryID,
      );
      await toggleError(false);
      // We can now inspect <Example /> with ability to toggle again
      inspectedElement = await inspect(1);
      ement.canToggleError).toBe(true);
      ement.isErrored).toBe(false);
      
        targetErrorBoundaryID,
      );
    });
  });
});