How nimarion/timing-stream-overlay works
Project type and purpose
• This is a front-end single-page application (SPA) built with React, TypeScript and Vite, designed to run as a browser-source overlay in streaming software (e.g., OBS).
• Its purpose is to display live event data—timing and wind speeds, race results, start lists, reaction times and upcoming events—by fetching from an external timing API or data service and rendering it in different on-screen “pages.”
File structure
• Top level: configuration files (.eslintrc.cjs, tsconfig.json, tailwind.config.js, vite.config.ts), index.html and package.json.
• src/: application code
• src/pages/: route-level components (reactions.tsx, results.tsx, etc.)
• src/components/: reusable UI components (CountryFlag, ResultsTable, WindIcon, etc.)
• src/router.ts: SPA routing setup
• src/utilts.ts and src/country-utils.ts: data-transformation helpers
• src/country-mapping.json: static lookup data
• src/main.tsx and src/index.css: React entry point and global styles
README for additional insights
• Features: lists the various overlay “pages” and shows screenshot examples.
• No internal service code: the app relies on an external data source (likely a REST or WebSocket timing API).
• Deployment: intended for live streaming events (hosted on a CDN, loaded into OBS).
Focus points
• Be granular: break out each page (Live Time, Results, Startlist, etc.) if the engineer needs that detail.
• Data-flow direction and refresh intervals (polling or websockets).
• That there is no backend in the repo: data is fully external.