Don't treat a route as a resource route if it only has an ErrorBoundary

[brophdawg11]

What version of Remix are you using?

1.15.0

Are all your remix dependencies & dev-dependencies using the same version?

• Yes

Steps to Reproduce

import {
  Outlet,
  isRouteErrorResponse,
  useRouteError,
} from "@remix-run/react";

// this is required to make this a UI route, but we should be able to 
// default to this if no default is exported but a boundary is
// export default Outlet;

export function ErrorBoundary() {
  let error = useRouteError();
  // ...
}

Expected Behavior

Any route exporting a default component, ErrorBoundary, or CatchBoundary is considered a UI route.

Actual Behavior

Only routes exporting a default component are considered a UI route.

[kiliman]

Interesting. I wonder what scenarios you would want to export an ErrorBoundary but not a default UI component.

To me, I think it should be an error instead of treating it as a resource route, since they don't have UI.

[brophdawg11]

The use-case I've seen is a singular top level error boundary in a pathless route below root - so it can still access valid loader data from the root loader (i18n info, etc.). I think that might be the use-case Ryan was doing when he ran into it today.

[brophdawg11]

Fixed in #6125 - should be released in Remix 1.16

[github-actions]

🤖 Hello there,

We just published version v0.0.0-nightly-e696522-20230422 which involves this issue. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!