In the past, this was inside the React "world" and it triggered a React Error Boundary, displaying a nice error for the user. But this caused issues when configuring Axios interceptors due to React's Strict Mode double render.
This is the PR that fixed the double render/interceptor issues: #250
But we've lost the ability to display a nice error message to the user. Everything (the intern) suggest we should just modify the website HTML programatically in that scenario:
https://chatgpt.com/share/685aa1f4-14b4-8013-96f7-ee6537b93e7a
In the past, this was inside the React "world" and it triggered a React Error Boundary, displaying a nice error for the user. But this caused issues when configuring Axios interceptors due to React's Strict Mode double render.
This is the PR that fixed the double render/interceptor issues: #250
But we've lost the ability to display a nice error message to the user. Everything (the intern) suggest we should just modify the website HTML programatically in that scenario:
https://chatgpt.com/share/685aa1f4-14b4-8013-96f7-ee6537b93e7a