LFC.se

Monorepo for the unofficial https://www.lfc.se companion app and its backend services.

Structure

This is a pnpm workspace orchestrated with Turborepo.

apps/
  mobile          @lfc/mobile        Expo / React Native app
  worker          @lfc/worker        Hono backend for scheduled/background jobs (Vercel + Inngest)
packages/
  api             @lfc/api           Transport-agnostic lfc.se API client + types

Getting started

pnpm install            # install every workspace
pnpm dev                # run all dev servers (turbo)
pnpm typecheck          # typecheck every package
pnpm lint               # lint every package
pnpm format             # check formatting (oxfmt)

Target a single package with a filter:

pnpm --filter @lfc/mobile dev          # expo start
pnpm --filter @lfc/worker dev          # local Hono server

CI/CD

Two GitHub Actions workflows live in .github/workflows:

Workflow	Trigger	What it does
ci.yml	pushes to main, pull requests	pnpm format, lint, typecheck
eas-build.yml	manual dispatch, tags matching v*	starts an EAS build of @lfc/mobile

To run a build by hand, open Actions → EAS build → Run workflow and pick a platform and an eas.json profile; pushing a v* tag builds production for both platforms. Builds are started with --no-wait, so the workflow finishes as soon as EAS has queued the job — track progress on expo.dev.

The build workflow needs an EXPO_TOKEN repository secret (Settings → Secrets and variables → Actions), created from a personal access token at expo.dev/settings/access-tokens.

Because @lfc/api is consumed from its compiled dist/, @lfc/mobile has an eas-build-post-install hook that builds it on the EAS worker after install.

Apps

📱 @lfc/mobile

The Expo app: news, games, standings, comments and push notifications. See apps/mobile.

⚙️ @lfc/worker

A small Hono service, deployed to Vercel, that runs scheduled background jobs via Inngest. Right now that's polling lfc.se for new articles and pushing them to the mobile app via Expo Push — replacing the old on-device background poll (which the OS throttled heavily) with prompt server-driven delivery — but it's meant to grow to hold other background jobs too. Setup and deployment: apps/worker/README.md.

Notifications, end to end

1. On launch (with notifications enabled) the mobile app registers its Expo push token with the backend (POST /api/devices).
2. Inngest runs the backend's poll function on a schedule (every 5 min).
3. The backend fetches the latest articles via @lfc/api, compares them to the articles not yet announced, and sends an Expo push for each new one.
4. The app receives the push and deep-links to the article on tap.

If no backend is configured (EXPO_PUBLIC_NOTIFICATIONS_API_URL unset) or it's unreachable, the app falls back to its on-device background poll, so notifications still work — just less promptly.