When pages/page.tsx
have a problem, redirect to 404 happen without any errors or warnings
#12645
Unanswered
oleksii-lukin
asked this question in
Help
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I restored some files from previous commits before big refactoring, which obviously contained some errors and wrong paths in them.
What happened is that my homepage started triggering 404 without any errors or warnings either in console or in browser console when I run
next
. After runningnext build
I finally got my errors and found what I need to fix so everything starts working again.What is not clear to me is how to prevent this situation in future - I'm running dev mode, I expect not only get errors but any warnings, instead I was given no information at all and just 404. I wasn't even opening that broken page, just trying to open homepage, and getting 404 instead.
Why 404? I tried to look up how to list all routes, but it seems not possible? How do I know why 404 is happening if I don't have this information? It wasn't 404 so why it's silenced and I get no error. I haven't used any
--no-verbose
flags afaik.Is this a bug or it's how it's supposed to work?
Beta Was this translation helpful? Give feedback.
All reactions