root 68b0bf4b91 Fix the locale bug and the shared-metadata race behind the lint errors
services.tsx fetched /api/website/services/undefined, because the locale
cookie was read with a check that is false for the empty string and then fell
through unguarded. The endpoint is /api/website/services/{locale}. It also
ignored response.ok and assumed a payload shape, so a failing API threw. All
three are covered by a new regression test; the suite was 2 failures before
and passes 10/10 now.

The filtered-posts page rewrote fields of an exported module-level `metadata`
object during render. That object is a singleton shared by every request in the
process, so concurrent visits to different filters could serve each other's
title, description and OG image, and Next reads the export at build time so the
runtime writes were largely discarded anyway. Values now live in an immutable
record and generateMetadata returns a fresh object per request.

Also replaces set-state-in-effect locale reads with a useSyncExternalStore hook
over the cookie store, derives the active project category instead of storing
it in state (so it self-heals when the data or locale changes), makes the
"random" not-found picks stable per path instead of Math.random() during
render, and tightens a few `any` types.

eslint goes from 36 errors to 0, tsc stays clean.
2026-10-01 17:15:12 -04:00
2026-06-28 15:45:32 +00:00
2024-11-11 12:44:23 +03:30
2024-11-20 16:38:40 +03:30
2024-11-20 16:38:40 +03:30
2024-09-15 10:08:29 +03:30
2024-11-16 17:07:57 +03:30

This is a Next.js project bootstrapped with create-next-app.

Getting Started

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.

This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.

Learn More

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.

S
Description
No description provided
Readme
42 MiB
0 Stars 1 Watchers 0 Forks
Languages
TypeScript 97.5%
JavaScript 1.5%
CSS 1%