mariheck/tech-news

tech.news

A weekly, AI-curated digest of latest news in frontend development, design engineering, web design, and AI. Each article recaps one or more external sources and can be read in 10 minutes or less.

UI copy is French (lang="fr"); code, comments, and docs are English.

Stack

• Next.js 16 (App Router)
• React 19 with the React Compiler
• TypeScript 5
• Tailwind v4
• Vitest 4 + jsdom + @testing-library/react
• ESLint 9

Getting started

npm install
npm run dev

Open http://localhost:3000.

Scripts

| Command | What it does | | ----------------------- | ----------------------------------------- | | npm run dev | Dev server on port 3000 | | npm run build | Production build (also runs the TS check) | | npm run start | Serve the production build | | npm run lint | ESLint | | npm run test | Vitest in watch mode | | npm run test -- --run | Single Vitest pass (CI-style) |

There is no typecheck script — next build typechecks, or run npx tsc --noEmit for a fast standalone check. A green test run does not guarantee types pass (Vitest skips type errors).

Project layout

• app/ — App Router routes (home, archives, [date]/[slug] articles, mentions-legales). Server Components by default; 'use client' opts into client behavior.
• components/ — shared UI grouped by surface (article/, category/, decoration/, layout/, listing/, navigation/, shared/, typo/). Named exports re-exported through a per-group index.ts barrel.
• content/ — editorial content on disk (see below).
• types/ — shared TypeScript types (@/types barrel).
• utils/ — loaders, formatters, and category lookups (@/utils barrel).
• __tests__/ — Vitest specs at the repo root, mirroring t