tamer-dev-app

Standalone Tamer4Lynx dev app — Expo Go-style QR scan and HMR.

This is a private monorepo workspace app, not an installable npm package for downstream projects.

Installation

This package is the native host app for development. It is typically used as a workspace package in the tamer4lynx monorepo.

# From tamer4lynx root
t4l build android --install
t4l build ios --install

Usage

1. Run the dev server: t4l start (from project root)
2. Build and install the dev app: t4l build android --install or t4l build ios --install
3. Open the dev app on your device, scan the QR code, and connect to the dev server for HMR

The dev app embeds tamer-dev-client for the launcher UI, discovery, and reload bridge.

Rspeedy dev server compatibility

The dev app can scan a QR code or manually enter a URL from a plain rspeedy dev server and load the bundle directly — no t4l start needed. Since rspeedy does not serve a /status endpoint, the dev client's probe falls through to a direct HEAD /main.lynx.bundle check and loads the bundle via openProjectDirect.

What works: bundle loads, live reload via rspeedy HMR. What requires t4l start: Tamer meta.json, native module compatibility checks, Tamer WebSocket HMR bridge, multi-bundle support.

Platform

Uses lynx.ext.json. Android and iOS native projects are generated by t4l create and linked via t4l link.

Native linking (important)

ios/TamerDevApp/LynxInitProcessor.swift is not pre-filled with module imports/registrations. Placeholders (GENERATED IMPORTS / GENERATED AUTOLINK) are updated when you run t4l link (or t4l link ios / t4l link android) from this package directory (where tamer.config.json lives). In the monorepo you can use npm run link:native from packages/tamer-dev-app after building the CLI (npm run build at the repo root). Fresh clones must run link before iOS will compile.