A React App is usually one big component made up of smaller components. This makes for easy organization of code. A problem arises though when an...
For further actions, you may consider blocking this person and/or reporting abuse
Everytime you make a to-do app, a bird dies ! haha , so yeah we should use chat, search or what ever in our examples (even though you didn't really make a to do app) , jk
I didn't know we can make an error boundary component, I knew the ComponentDidCatch method but I just used it in a regular component once, as you see I'm a react beginner lol .
Anyway, I liked you article, great as always Sarah :)
Thank you😊
Thank you for posting like such a important blog.
Do you know how to show the full component stack like proper component names in production build?
I am not able to print full stacktrace either, it prints the minified names.
Thanks for sharing! Error boundaries are one of my favorite React 16 additions. I did not notice the second argument to componentDidCatch, I’ll check it out!
Yes, you should☺
I have created proptypes and want to catch the error if the prop type fails.I tried using this method but failed to catch the exception.Can you please help.
New to React started just few days back.