Add note about dev/build behavior to error boundaries docs
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
I'm using create-react-app and when I use an ErrorBoundary with componentdidcatch and run "npm start," my custom error message briefly flashes as intended, but then the regular developer error page shows after a second or so. There is no mention of this behavior on the docs page, so I spent a lot of time trying to figure out what I did wrong before I tried running the build version and saw it worked as expected (no default error page shown).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the Error Boundaries documentation page and reproduce the behavior with create-react-app using "npm start" and the build version. Add a note explaining that the developer error page may appear after the custom message in development, while the build version behaves as expected; confirm the documentation matches both modes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100