How adcident12/fpl-dashboard works
FPL Dashboard is a Fantasy Premier League decision-support web app: users inspect public FPL data and can enter team IDs for squad, transfer, captain, chip, and rivalry analysis. The main path is React app → API client → Express routes → FPL data and analysis → displayed views. The tree and excerpts establish the major views and backend capabilities, but do not show every view’s API calls or every analysis implementation, so those specific links are omitted.
Main entry points: App.jsx App navigation · api.js API client · RivalryView.jsx Rivalry view · fpl.js FPL data and analysis
Components 19
Dashboard client
- React entry
client/src/main.jsx - App navigation
client/src/App.jsx - Player table
client/src/TableView.jsx - Fixture views
client/src/FixtureGrid.jsx - Squad view
client/src/SquadView.jsx - Recommendations
client/src/SuggestionsView.jsx - Chip planner
client/src/ChipsView.jsx - Live bonus
client/src/BonusView.jsx - Rivalry view
client/src/RivalryView.jsx - Set-piece view
client/src/SetPiecesView.jsx - Dream Team view
client/src/DreamTeamView.jsx - Saved team IDs
client/src/useTeamId.js
HTTP API
- API client
client/src/api.js - Express routes
server/index.js
FPL data and analysis
- FPL data and analysis
server/fpl.js
Cached state
- Disk cache
server/cache.js
Other components
- Dashboard user
- Public FPL API
- Cache files
Connections 20
- Dashboard user → React entry: opens dashboard
- React entry → App navigation: renders
- App navigation → Player table: selects view
- App navigation → Fixture views: selects view
- App navigation → Squad view: selects view
- App navigation → Recommendations: selects view
- App navigation → Chip planner: selects view
- App navigation → Live bonus: selects view
- App navigation → Rivalry view: selects view
- App navigation → Set-piece view: selects view
- App navigation → Dream Team view: selects view
- App navigation → API client: fetches players
- Recommendations → API client: requests analysis
- Rivalry view → API client: requests squads
- API client → Express routes: HTTP requests
- Express routes → FPL data and analysis: dispatches data and analysis
- FPL data and analysis → Public FPL API: fetches FPL data
- FPL data and analysis → Disk cache: reads and writes
- Disk cache → Cache files: persists entries
- Rivalry view → Saved team IDs: saves team IDs