Issues with making a working production build

v0
, ,
1

I’ve recently made a documentation website pretty similiar to gitbook using v0.dev, in dev build (preview) it works perfectly fine but in production build the navbar, footer, sidebar shows up, but the main component (the website itself) shows up as 404 error - client console says that loading the 1:/home page returned an 404, i’ve been trying to fix this for the past few days, used up over 10$ in credits fixing an error by v0.dev and still doesn’t work, i’ve tried manually fixing it, didn’t help, i’ve tried prompting the AI to fix it providing errors i get, didn’t help neither, i’ve tried using enhanced prompts on top of the ones i did before, didn’t help neither. I’am also getting an build warning with deploying to production saying the following :

06:01:44 :warning: `eslint` configuration in next.config.mjs is no longer supported. See more info here: CLI: next CLI | Next.js

06:01:44 :warning: Invalid next.config.mjs options detected:

06:01:44 :warning: Unrecognized key(s) in object: ‘eslint’ 06:01:44 :warning: See more info here: Invalid `next.config.js` | Next.js

Anyone could help me out ? PS: The website is https://docunaut.vercel.app so u can checkout what breaks and so u can check console logs on client.

And here is the dev build and the chat itself where yall can remix it from and try fixing it https://v0.app/chat/code3-GLbKMHkXsD1?b=v0-preview-b_pPyrItYYqPD&f=1&path=%2F

But please, do not overtake it, u can use it for your own project if u fix it, but just don’t say u made it.

Best regards,

Iceyy.

4

Hello,

I’m trying to take a look here but everything seems to be working, the whole docunaut.vercel.app site is functional and I can navigate everywhere successfully

Are you still seeing errors? If so can you link to specifically where they are?

image
image1920×1200 133 KB

5

Wierd, now it’s working, previously it always gave an 404 error page, while still showing the navbar, side bar and footer + in the client console it shown an 404 error loading the /home page.

6

Additionally, this is what i’ve seen before.

image
image1912×943 15.5 KB

7

That kind of 404 should only appear when you manually call notFound() inside a nested route segment, so I’d look into whichever component looks like it’s responsible for that portion of the screen (appears to be including everything below the header and outside the sidebar) and see if you have something calling notFound()

If it’s fetching data remotely, maybe there was an error in the response earlier that’s not there anymore

1 Like