Bug report: Single fetch: Throwing a response stub with a 3xx status from a resource route results in an unexpected server error

[haines]

We had a couple of routes that were only there to redirect to another page in the application, and I forgot to put a default export in the modules.

We discovered that for these routes, the redirect works for data requests, but not for document requests.

I'm guessing this may just be the same problem as in #9471, but it manifests differently (presumably because without a default export it's not treated as a UI route). Instead of a turbo-stream error, the response stub propagates all the way to returnLastResortErrorResponse and we get the plaintext 500 Unexpected Server Error page.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5cf4966

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[brophdawg11]

Thank you for the bug report! This is handled by #9488

[brophdawg11]

And also has some additional test cases added in #9501

[jam-fran]

I'm using 2.10.2 and am still experiencing this bug. Here I had my index route that is intended to be a pure redirect:

export const loader = defineLoader(async ({ response }) => {
  response.status = 302
  response.headers.set('Location', '/account')
  return null
})

When this was the only export in my route file, I got an Internal Server Error on document requests.

When I added an empty default export:

export default function IndexRoute() {}

It worked as expected.

[brophdawg11]

I cannot reproduce that in a simple reproduction: https://stackblitz.com/edit/remix-run-remix-bydt2f

Could you open a new issue with a minimal reproduction of the issue?