Simulate component crashes and test your fallback UIs instantly. No need to write 'throw new Error()' in your code.
Verifying that your error boundaries correctly catch and display fallbacks usually requires temporarily adding buggy code to your source.
DevConsole allows you to select a component in the tree and force it to throw an error during the next render or event cycle.
Use the component picker to highlight the area of your app you want to 'break'.
Inject a runtime error into that component's next render.
Watch your Error Boundary catch the error and display the correct fallback UI.
No, it's designed to test internal app recovery. If the error isn't caught, the page may crash as expected.
Yes, you can also use DevConsole to force specific API calls to return 500 errors to test data-fetching boundaries.
Explore more ways to use DevConsole to speed up your development
DevConsole is free during development. Join 5,000+ developers shipping better code.
Get Started Now