Hey,
I found this remix-island issue posted on remix-run repo. I get the same issue in our app since upgrading to Remix v2. The problem is that any unhandled errors in any loader on initial load causes rendering problems in ErrorBoundary, which doesn't happen on client-side navigation. The ErrorBoundary triggered is not the one in root.tsx which unmounts the whole document, the problem still exists when we render an extra ErrorBoundary in a pathless route below root, which we call __Layout.
One of the Remix maintainers suggests in a reply it's likely caused because the reporter uses remix-island and it removes SSR errors.
Is deleting of these errors necessary for remix-island to work correctly? 🤔
Hey, I found this remix-island issue posted on
remix-run
repo. I get the same issue in our app since upgrading to Remix v2. The problem is that any unhandled errors in any loader on initial load causes rendering problems inErrorBoundary
, which doesn't happen on client-side navigation. TheErrorBoundary
triggered is not the one inroot.tsx
which unmounts the whole document, the problem still exists when we render an extra ErrorBoundary in a pathless route below root, which we call __Layout.One of the Remix maintainers suggests in a reply it's likely caused because the reporter uses remix-island and it removes SSR errors.
Is deleting of these errors necessary for remix-island to work correctly? 🤔