How irislib/iris-client works
Project type and purpose
• This is a single‐page, full‐client social networking/webchat application (“Iris”) built with TypeScript and React (via Vite).
• It ships as a static SPA (index.html + JS/CSS bundles) and communicates at runtime with decentralized back‐ends (Nostr relays, WebRTC peers) and various third‐party embed services.
File structure
• Top‐level “src” holds all UI pages and shared components; “public” holds built assets and static files.
• There is no monolithic server code here—build is handled by Vite and served as static content (Dockerfile + docker-compose.yml suggest an Nginx or similar static‐file container).
• “config” contains environment/relay settings; “scripts” and “tests” folders define automation and E2E test suites.
• CI is defined under .github/workflows; Playwright/E2E runs against the deployed static site.
README
• Confirms that this is a front‐end client for iris.to, built and tested via Yarn/Vite, and deployed as a static site.
• No internal database or backend service code—runtime data comes from Nostr and WebRTC sessions.
Detail
• Major folder or module as a sub‐component (e.g., “Chat module,” “Feed module,” “Embed engine”).
• Caching layer (memcache.ts) and configuration loading.
• Test harness (Playwright) as an external actor that runs against the deployed SPA.