BikeControl (SwiftControl)
Use Zwift Click, Zwift Play, Shimano Di2, or any Bluetooth controller with MyWhoosh, Rouvy, Zwift, and more. Free to try on iOS, Android, Windows, and macOS.
Free Fantasy Premier League analytics: expected points projections, transfer planning, fixture difficulty, captaincy and chip strategy for every gameweek.
Sports & fitnessTypeScript · PLpgSQLGitHub @Dsinha97OnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
GitHub star growth between the latest completed 8-hour observations
Use Zwift Click, Zwift Play, Shimano Di2, or any Bluetooth controller with MyWhoosh, Rouvy, Zwift, and more. Free to try on iOS, Android, Windows, and macOS.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
FPL Decision: Fantasy Premier League analytics and decision support
Translation pending
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
Personal Fantasy Premier League analytics and decision-support application. A static Next.js front
end on Cloudflare, with Supabase Postgres and Edge Functions behind it.
Live at fpldecision.com.Read the full README ↗Personal Fantasy Premier League analytics and decision-support application. A static Next.js front end on Cloudflare, with Supabase Postgres and Edge Functions behind it.
Live at fpldecision.com.
roadmap.md, as is
docs/sources/fpl_app_phase_wise_build_plan.md, the original
architecture document phases 0–4 were built fromAn expected-points model runs in Postgres over the FPL API's data, and the front end turns it into decisions rather than dashboards:
TeamState, with a
replacement finder for any single pickTwo rules shape the numbers throughout. Where FPL zeroes a field between seasons, the term is dropped and the remaining weights renormalised, with a note in the UI next to the figure — never multiplied by zero and quietly shrunk. And a number is labelled for what it is: downgrades are called downgrades, an assumption is shown as its own term, and an empty result set says so rather than ranking five worse options.
main by Cloudflare's Git integrationnpm install
cp .env.example .env.local # fill in your Supabase project URL + publishable key
npm run dev
Open http://localhost:3000.
The browser only ever reads, and only over the publishable key — every write path is an Edge Function running with the service role, so the client bundle needs no other secret.
npx tsc --noEmit # typecheck — run before every commit
npm run lint
npm run build # static export to out/ — must pass before pushing
app/ — routes (/ /team /players /fixtures /news /builder /scenarios
/transfers /compare /status)lib/ — the model layer: team-state.ts plus the optimiser, lineup, scoring, squad-score,
transfer and transfer-optimiser engines. All pure, so they are testable without React or networkcomponents/ — UI components (shadcn/ui-style primitives in components/ui)supabase/migrations/ — versioned schema changessupabase/functions/ — Edge Functions (ingestion, predictions). Deno, and deliberately excluded
from tsconfig and eslint, or tsc --noEmit breaks on Deno globals.github/workflows/ — CI only (ci.yml). The deploy lives on Cloudflarewrangler.jsonc — Cloudflare Worker config: static assets from out/, no server scriptPushing to main triggers a Cloudflare build from the Git integration: npm run build, then
wrangler deploy serves out/ as static assets per wrangler.jsonc. Node comes from .nvmrc.
NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY must be Cloudflare Build
variables, not runtime bindings — a static export bakes them in at build time, and
lib/supabase/client.ts calls createClient at module scope, so a missing one fails the build
outright rather than degrading. The same two values are GitHub Secrets for ci.yml, which builds as
a quality gate without deploying.
Two things the Cloudflare setup wizard gets wrong for this project: it defaults the build command to
the OpenNext adapter (npx opennextjs-cloudflare build), which targets server-rendered Next and
fails on a static export, and it offers no base path — correctly, since the site is served from a
domain root. There is deliberately no basePath in next.config.ts any more.
Every schema change is a versioned SQL file in supabase/migrations/, applied to the Supabase
project and committed here. Migrations and function deploys go through the Supabase MCP OAuth
integration — the database password is never requested, stored, or accepted.
Source code is MIT; written content, branding and third-party data are excluded. See LICENSE.