Programming standards
JavaScript / TypeScript
TS strict, React/Next.js, async, lint, structure and secure patterns.
- 0110 minTypeScript strict — why and howintro
Strict mode as the ProfessNet standard and how to avoid any in the ZEUS frontend.
- 0212 minReact / Next.js project structure (App Router)core
How we organize directories, components and the server/client boundary in the ZEUS frontend.
- 0311 minAsync, Promises and error handlingcore
async/await, parallelism and fetch error handling in the ZEUS frontend.
- 049 minESLint + Prettier (team standard)intro
Division of roles: Prettier formats, ESLint guards quality — the ProfessNet configuration.
- 0512 minSecure patterns (validation, XSS, secrets)advanced
zod validation, XSS protection and correctly handling secrets in Next.js.
- 0612 minTests (Vitest / React Testing Library)core
How we test the logic and components of the ZEUS frontend: Vitest + React Testing Library.
Check your knowledge — quiz
5 questions · pass mark 80%. Score saved locally.
1.Under the ProfessNet standard, what do we use instead of any at the boundary with the outside world (API, localStorage)?
2.How do components render by default in the Next.js App Router, and when do we add "use client"?
3.Why, after calling fetch, must we check res.ok and explicitly throw an error for 4xx/5xx statuses?
4.In the ESLint configuration, what does the no-floating-promises rule set as error mean?
5.Which environment variable in Next.js reaches the bundle and is visible in the browser?