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.
Start, bench and add/drop help for Yahoo Fantasy NBA
Sports & fitnessTypeScript · CSSGitHub @mingray0121OnlineOwner 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
A web application serve as the gm to help make fantasy decisions.
Translation pending
Loading the full README.
Read the full README ↗Start / bench / add / drop help for Yahoo Fantasy NBA. One user, many leagues, each league isolated with its own versioned rules. Next.js (TypeScript) on Vercel, Neon Postgres, GitHub Actions for the refresh jobs.
Every recommendation comes from one idea: a per-player value under that league's scoring, multiplied by the games that player actually has.
| Path | What it is |
|---|---|
src/db/schema.ts | Drizzle schema, 22 tables (21 from the design plus player_id_overrides) |
drizzle/ | Generated SQL migrations (npm run db:generate after schema changes) |
src/lib/yahoo/ | OAuth 2.0 (tokens AES-256-GCM encrypted at rest) and a read-only Fantasy API client + JSON parsers |
src/lib/nba/ | Schedule and box scores from ESPN's public API (the NBA CDN blocks cloud hosts and non-US networks), balldontlie fallback, behind one NbaDataSource interface |
src/lib/rules/ | Rule format (JSON and CSV upload), validation, normalization of Yahoo stat names and slots |
src/lib/engine/ | Pure logic: projections, points / z-score values, exact lineup optimizer, matchup projection, add/drop pairing |
src/lib/data/ | Per-league data loading and the read models behind each page |
src/lib/jobs/ | Refresh jobs and the registry the scheduler calls |
src/app/ | Pages (Today, Week, Matchup, Add / drop, Rules, Settings, Roster for manual leagues, Player) and API routes |
.github/workflows/ | CI plus scheduled jobs that call /api/jobs/* |
test/ | Unit tests, plus an integration test that runs against a real Postgres |
Both category (H2H and roto) and points leagues are supported; each league's active rule version decides.
Rules import from Yahoo when you connect a league and again every morning; a new version is saved only when something changed. You can also edit them as JSON or upload a file on the Rules page. Each change is a new version for that league only, and you can switch back to any earlier version.
JSON:
{
"scoring_type": "h2h_categories",
"categories": ["FG%", "FT%", "3PM", "PTS", "REB", "AST", "STL", "BLK", "TO"],
"roster_slots": {"PG": 1, "SG": 1, "G": 1, "SF": 1, "PF": 1, "F": 1, "C": 2, "UTIL": 2, "BN": 3, "IL": 2},
"games_played_limit": null,
"max_adds_per_week": 4
}
A points league uses "scoring_type": "h2h_points" and "point_weights": {"PTS": 1, "REB": 1.2, "AST": 1.5, "STL": 3, "BLK": 3, "TO": -1} instead of categories.
CSV (header type,key,value):
type,key,value
setting,scoring_type,h2h_points
setting,games_played_limit,
setting,max_adds_per_week,4
point,PTS,1
point,TO,-1
slot,UTIL,10
slot,BN,3
Stat keys: PTS, REB, OREB, DREB, AST, STL, BLK, TO, 3PM, 3PA, FGM, FGA, FTM, FTA, DD, TD, MIN, PF, +/-, FG%, FT%, 3P%, A/T (Yahoo names like ST and 3PTM are accepted too).
Any other category can be defined in JSON from the counting stats above, as a sum or a ratio (ratios are scored by impact, like percentages; add "negative": true when lower is better):
{
"categories": ["PTS", "STOCKS", "AST/PF"],
"custom_stats": {
"STOCKS": {"sum": ["STL", "BLK"]},
"AST/PF": {"ratio": ["AST", "PF"]}
}
}
Create an app at https://developer.yahoo.com/apps/create/:
https://<your-vercel-domain>/api/auth/yahoo/callback. Yahoo requires HTTPS, so for local work either use the deployed URL or a tunnel (for example ngrok http 3000) and register that URL.DATABASE_URL..env.example (YAHOO_CLIENT_ID, YAHOO_CLIENT_SECRET, YAHOO_REDIRECT_URI, TOKEN_ENCRYPTION_KEY, SESSION_SECRET, JOB_TOKEN, optionally ALLOWED_YAHOO_GUID and BALLDONTLIE_API_KEY).vercel.json runs drizzle-kit migrate before next build, so the schema is created on the first deploy.ALLOWED_YAHOO_GUID is set; nobody else can sign in afterwards.Yahoo now approves Fantasy API access per app (apply at https://sports.yahoo.com/developer/access/). Until then:
APP_PASSWORD in Vercel (and .env.local) and sign in with it. The first Yahoo sign-in later links your Yahoo account to the same owner, so nothing is lost.players job), with positions and injuries.In the GitHub repo: Settings → Secrets and variables → Actions, add:
APP_URL: e.g. https://your-app.vercel.appJOB_TOKEN: same value as in VercelThen run Actions → jobs-nightly → Run workflow once to load the schedule and box scores. Schedules (UTC, covering US Eastern in both daylight and standard time):
| Workflow | When | Jobs |
|---|---|---|
jobs-game-day | every 15 min, 14:00–04:59 UTC | roster-sync, injuries, values |
jobs-hourly | hourly / every 2 hours | matchup-sync / free-agents, values |
jobs-nightly | 09:00 UTC | box-scores (×3 for catch-up), projections, values |
jobs-nightly | 10:00 UTC | schedule, rules-import, roster-sync, free-agents, values |
League jobs loop through your leagues one at a time, so one failing league never blocks the others. Every run is logged in sync_runs. The Refresh button in the app runs roster, free agents, matchup and values for just that league.
This is a TypeScript / Node.js project, so there is no Python venv or Poetry. The npm equivalents:
| Python | This project |
|---|---|
pyenv / .python-version | nvm / .nvmrc (Node 22) |
venv | node_modules/ inside the project folder (created by npm install, git-ignored) |
pyproject.toml | package.json |
poetry.lock | package-lock.json (exact versions; commit it) |
poetry install | npm ci |
poetry add x / poetry add --group dev x | npm install x / npm install -D x |
poetry run x | npm run x / npx x |
Everything installs into the project folder, never globally, so it is already isolated like a venv.
1. Install Node 22 with nvm (once per machine):
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash # or: brew install nvm
nvm install # reads .nvmrc
nvm use
2. Install dependencies (exact versions from package-lock.json):
npm ci
3. Environment variables. Copy the template and fill it in. .env.local is git-ignored and never leaves your machine:
cp .env.example .env.local
You need a Postgres database for DATABASE_URL: a Neon branch (free), or a local one, e.g. brew install postgresql@16 && createdb nfa then DATABASE_URL=postgres://localhost/nfa. A localhost URL uses the node-postgres driver instead of Neon's.
For Yahoo sign-in locally, Yahoo requires an HTTPS redirect: run a tunnel such as ngrok http 3000, register https://<tunnel>/api/auth/yahoo/callback on your Yahoo app, and put the same URL in YAHOO_REDIRECT_URI.
4. Create the tables, run the app, run jobs:
npm run db:migrate # applies drizzle/ migrations to DATABASE_URL
npm run dev # http://localhost:3000
npm run job -- schedule # load the NBA schedule
npm run job -- box-scores # box scores (repeat to catch up)
npm run job -- projections
npm run job -- roster-sync 1 # league jobs take a league id
Checks:
npm run typecheck
npm test
npm run build
npm test # unit tests
TEST_DATABASE_URL=postgres://postgres@localhost/nfa_test npm test # plus the integration test (truncates tables!)
sync_runs.error and in the Refresh response.player_projections.horizon) rather than pre-blended horizons, because the window weights are a per-league setting. Values per horizon (next game, rest of week, rest of season) live in player_values.player_id_overrides.