Wrong http status code (500) returned instead of 404 or any response thrown from a loader. about blues-stack HOT 9 CLOSED

This should be fixed with Remix 1.12.0 which should be out in the next hour or two

from blues-stack.

I don't think that this is the same issue.
It also happens in development.
And even in production a page that doesn't exist should send a 404, not a 500.
The behavior differs from previous remix versions and from running it with remix serve.

from blues-stack.

Minimal reproduction here: https://stackblitz.com/edit/node-zxrwpd

from blues-stack.

One thing that solves the issue is to remove the eslint --bundle flag here

from blues-stack.

This is an intended behavior in production, see Matt's answer here: remix-run/remix#5115 (comment)

from blues-stack.

The issue does not happen when not using eslint's --bundle flag or running server.ts with ts-node directly.

from blues-stack.

This looks like an issue with the bundling approach causing multiple disparate ErrorResponse classes to exist and this causing internal instanceof ErrorResponse checks to fail. We'll need to change those checks to avoid using instanceof for bundling approaches like this and instead use prop detection

from blues-stack.

The above merged PR will go in the next react router release, either 6.7.1 or 6.8.0 depending on what is in it. Then Remix will pick that up in it's next release.

from blues-stack.

Thanks for the quick fix!

from blues-stack.