TypeScript / AngularCompleted

League Stats

An Angular-based League of Legends performance dashboard. Search Riot IDs across 11 regions, analyse ranked statistics and match histories, inspect champion builds and objectives, follow live games, and save favourite players locally.

TypeScript 5.9Angular 21RxJSAngular SSRRiot Games APIData DragonHTMLCSS
LSLeague Stats
TypeScript 5.9Main technology
62Tracked files*
8Stack items
—Additional metric

*Verified tracked source and project files (build directories excluded)

01 · What it does

What the application does

Capabilities documented in the repository; the supporting sources and project configuration determine how they run.

01

Summoner lookup across 11 supported regions using Riot IDs

Summoner lookup across 11 supported regions using Riot IDs.

02

Match history with KDA, champion builds and performance summaries

Match history with KDA, champion builds and performance summaries.

03

Detailed match data, timeline events and gold/objective breakdowns

Detailed match data, timeline events and gold/objective breakdowns.

04

Live match team composition and summoner spells

Live match team composition and summoner spells.

05

Per-champion performance and locally saved favourite players

Per-champion performance and locally saved favourite players.

06

Angular signals, RxJS and an API proxy for Riot services

Angular signals, RxJS and an API proxy for Riot services.

02 · Technical structure

How the system works

01

Angular 21 standalone components organise pages for search, summoners, matches, current games and favourites.

02

RiotApiService communicates through a /api/riot proxy; routing/region helpers determine the right API server.

03

RxJS Observables and component state drive UI updates; Data Dragon supplies static game assets.

Riot data and Angular application flow

The README documents Riot ID searching across 11 regions, match history, champion metrics, live games and locally saved favourites.

01

Summoner and match lookup

A Riot ID (GameName#TagLine) selects the player and region, after which match history can expose KDA, builds, objectives and detailed match timelines.

02

Frontend and data services

Angular 21 components and Signals sit alongside RxJS and a Riot API proxy. Data Dragon provides champion and item assets separately from player statistics.

Documentation: GitHub repository / project specification. The content describes documented behaviour or plans; deployment readiness is not inferred.

04 · Source and design

Implementation examples and code walkthrough

Selected fragments from project source files with an explanation of the responsibility they implement.

Local favourites with Angular signals

TypeScript

Reactive UI state is mirrored into browser storage only when running client-side.

Frontend/src/app/core/services/favorites.tsSelected source excerpt
favorites = signal<FavoritePlayer[]>(this.read());
constructor() {
  if (this.isBrowser) {
    effect(() => {
      try { localStorage.setItem(this.LS_KEY, JSON.stringify(this.favorites())); }
      catch {}
    });
  }
}

Typed Riot API gateway

TypeScript

A typed HTTP abstraction sends platform-specific requests through a local API proxy and encodes user-controlled route parameters.

Frontend/src/app/core/riot-api.tsSelected source excerpt
@Injectable({ providedIn: 'root' })
export class RiotApiService {
  private http = inject(HttpClient);
  private readonly BASE = '/api/riot';

  summonerByPuuid(platform: string, puuid: string): Observable<SummonerData> {
    return this.http.get<SummonerData>(
      `${this.BASE}/${platform}/lol/summoner/v4/summoners/by-puuid/${encodeURIComponent(puuid)}`
    );
  }
}
TECHNICAL EVIDENCE

Source and implementation

Frontend/src/app/core/riot-api.ts · Abbreviated source excerpt

accountByRiotId(routing: string, gameName: string, tagLine: string) {
  return this.http.get<AccountData>(
    `${this.BASE}/${routing}/riot/account/v1/accounts/by-riot-id/${encodeURIComponent(gameName)}/${encodeURIComponent(tagLine)}`
  );
}
STATUS & SOURCE NOTES

Status & source limitations

Descriptions and examples are based on the repository documentation and selected source files. Build settings, external services, assets and project-specific configuration may be required to run the application.