[BUG]: Hydration error when navigating to /projects page

[AnshuPriya-1]

Bug Description

When navigating to the Projects page (/projects), the website throws a React hydration runtime error and the page fails to render correctly.

This happens consistently when clicking the "View All Projects" button on the homepage or directly opening /projects.

The error shown is:

Unhandled Runtime Error
Error: There was an error while hydrating.

This indicates a mismatch between server-rendered HTML and client-rendered HTML during hydration.

Steps to Reproduce

1. Clone the repository
2. Run npm install
3. Start the development server using npm run dev
4. Open http://localhost:3000
5. Click "View All Projects" on the homepage
   OR directly navigate to http://localhost:3000/projects
6. The hydration runtime error appears

Logs and Screenshots

Error message shown in the browser:

Unhandled Runtime Error
Error: There was an error while hydrating.
Because the error happened outside of a Suspense boundary,
the entire root will switch to client rendering.

Screenshot attached for reference.

Environment Details

• OS: Windows 11
• Browser: Microsoft Edge / Chrome
• Node.js version: v22.19.0
• Next.js version: 14.1.3

Impact

Medium - Feature works but has issues

Code of Conduct

• I have joined the Discord server and will post updates there
• I have searched existing issues to avoid duplicates

[AnshuPriya-1]

Hi @Zahnentferner
I would like to work on fixing this issue if it is approved.

[AnshuPriya-1]

Thank you for assigning this issue to me. I’ll work on the fix and open a PR soon.

[AnshuPriya-1]

Hi @Zahnentferner
I investigated this issue locally and found that the root cause was unstable project ordering during render.

I also worked on a local fix for it, but after checking the latest upstream main, I found that this had already been resolved by the commit fix: resolve hydration error by using deterministic sort.

Because of that, after rebasing my branch, there was no meaningful functional change left to submit, so I am not opening a PR for this.

[AnshuPriya-1]

Hi @Zahnentferner,
Just following up on this issue. After syncing with the latest upstream main, I confirmed that the hydration problem has already been resolved by the deterministic sort fix, and I’m no longer able to reproduce it on the updated codebase.
Since there doesn’t seem to be any remaining change for me to submit here, this issue may be closed if that matches your assessment.
Thank you.