How kingkingburger/oinqueue works
Project type and purpose
• This is a full-stack web application built with Next.js (13+) using the App Router.
• Purpose: Fetch and display League of Legends summoner and match data (from Riot Games API), render player pages, match cards, champion summaries, etc.
File structure
• Top-level config files: next.config.ts, tsconfig.json, bun.lock, package.json – define build and runtime configuration.
• src/app: Next.js App Router entrypoints (layout.tsx, page.tsx, globals.css).
• src/(main)/(player)/page.tsx: dynamic route for individual player pages.
• src/component: reusable React components for UI (cards, headers, separators, lists).
• src/constant: shared constants (e.g. basic.ts).
• src/lib/riotApi: server-side helper functions to call external Riot API (getSummonerInfo, getMatchList, getMatchInfo) plus type definitions.
README for additional insights
• Standard Next.js boilerplate, deployed on Vercel, no internal database—data comes directly from Riot API.
Elements
• Clear labels: “Browser,” “Next.js App Server,” “src/lib/riotApi,” “Riot Games API,” “CDN / Static Assets”
• Browser → Next.js Server (page request)
• Next.js Server → Riot API (data fetch)
• Riot API → Next.js Server (JSON response)
• Next.js Server → Browser (HTML payload)
• Browser ↔ CDN (assets)