Error boundary still showing in production
See original GitHub issueIs this a bug report?
Maybe
Did you try recovering your dependencies?
1.16.0
Which terms did you search for in User Guide?
deoloy production create react app heroku error boundary overlay production error boundar showing on creater react app production
Environment
Environment Info:
System: OS: macOS 10.14.5 CPU: (4) x64 Intel® Core™ i5-6360U CPU @ 2.00GHz Binaries: Node: 8.16.0 - /usr/local/opt/node@8/bin/node Yarn: 1.16.0 - /usr/local/bin/yarn npm: 6.4.1 - /usr/local/opt/node@8/bin/npm Browsers: Chrome: 74.0.3729.169 Firefox: Not Found Safari: 12.1.1 npmPackages: react: ^16.8.6 => 16.8.6 react-dom: ^16.8.6 => 16.8.6 react-scripts: 3.0.1 => 3.0.1 npmGlobalPackages: create-react-app: Not Found
Steps to Reproduce
(Write your steps here:)
- Set up an error boundary around the app
- Deploy the production and staging app to heroku
- When the error it triggered, an overlay should not show up. This is not the case for both staging an production.
Expected Behavior
The error overlay should not show.
Actual Behavior
The error boundary shows in front of the fallback page.
Reproducible Demo
(Paste the link to an example project and exact instructions to reproduce the issue.)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:8
Top GitHub Comments
You’ll need to use the create-react-app buildpack on heroku: https://github.com/mars/create-react-app-buildpack
Thank you!!!