-
Something like that:
```tsx
import './index.scss';
// other imports
import { ErrorBoundary } from 'react-error-boundary';
```
And my setting is
```js
'import/newline-after-import': [
'errā¦
-
My test that was working when using the registry version of `apollo-mocked-provider@4.0.1` now fails after `npm link` in a local copy of this repo (both on latest master and b4e22ef) and `npm link apoā¦
-
### Current Behavior
nx nrwl seems to be causing issues with other packages like react 18.3.1 and grommet JS. React 18.3.1 and grommet JS work on their own just fine without nx nrwl. Older versionsā¦
-
Right now errors are returned as a part of the `useQuery` result. Maybe a better idea would be to throw them and recommend to use [Error Boundaries](https://reactjs.org/docs/error-boundaries.html#intrā¦
-
Create an Error Boundary component which renders a default fallback UI which shows the error in a user-friendly way.
Props API:
* children: ReactNode
* fallbackUI (default to something simple andā¦
-
Even though we use use Error boundaries throughout the app, there is no consistent way to surface these errors. Opening this issue to discuss the use of error boundaries, how we want to surface these ā¦
-
### Issue Description
This one took quite a while to get a minimal reproduction for since a lot of things have to be true for it to happen so I'll try to explain it all step by step as well as attachā¦
-
### Link to the code that reproduces this issue
https://github.com/dayblox/ppr-isr
### To Reproduce
1. Build the application (next build)
2. Start the application (next start)
3. Navigate to [locā¦
-
### Describe the Bug
Within TMTV mode when a user tries to create the "Rectangle ROI Threshold" to allow TMTV and SUV calculation a "Something Went Wrong" Error is popping up.
![image](https://gitā¦
-
I have been encountering a weird issue.
I have a react+typescript based project it was working fine.
Now, I migrated everything to nx-based mono-repo, and I'm getting the following error -
`ā¦