and it also shows the NEXT_NOT_FOUND message that is from the notFound call

so im not sure why it would't work

also is there a way to enable errors to be visible in prod too? i don't want the "security feature" that next gives for errors

throwing that error is just how notFound and redirect works, if you have a try catch, you should not have them inside or rethrow them

In my route I do something like

async function MyPage(){
    ...
    if(response.status === 404){
        return notFound()
    }
    ...
}

I don't catch the error elsewhere

o.O

and you on latest version right?

Yes

ok, i might look into this a bit more later... seems odd

To make this work I had to move the not-found to the parent folder (courses) and it caught the not found, but, in a segment route which is completely different from this one, I have the exact same situation with a not found inside a dynamic route, and that one catches the not found in that segment as I expected

It doesn't make any sense

Error handling in next is really painful xD

i haven't played with error.tsx much yet 😭

It's completely utterly useless

😢

Because you don't get the error that was thrown

So what are you gonna do with the error.tsx page? Write a "oopsie woopsie thewe was an ewwow"? The only context it gives you is that "there was an error" yeah thanks lmao

yeah its just meant to give a better screen for error times... but idk

Let me know if you find something

I guess I'll have to implement my own error component that returns a 200 status!

Since you can't override the status code of the response

i wonder if middleware can be abused ngl

Middlewares are a pain to handle, you need to keep track of so many more things at that point

yeah

But I might try

also does redirect work, or does error take that too

I'm just annoyed that it feels like they are not considering basic use cases of a framework, it really feels like the app router was made for static websites

I'm not on pc rn, I'm heading to bed, I'll check tomorrow

This is incredible