← Changelog
NewApps

ib-apps link: adopt a clone of the app's files without overwriting anything

A folder that already holds the app's files, such as a git clone or a copy from a teammate, is linked to the app with ib-apps link --app <slug>. Nothing is written: files that match the server are synced from then on, and the next push or dev sends what's only in the folder, fetches what's only on the server, and asks about a file that differs on both sides, with the usual diff. Before, the only ways in were pull --force, which replaced the folder with the server's copy, or push --app, which sent the folder as the whole app.

New apps also ship a root tsconfig.json (strict, covering web/, api/ and tests/ with the generated web/ib-client.d.ts), with TypeScript and the React and Node types among the dev dependencies, so your own editor type-checks the app the way the Files editor does, and npm run typecheck does the same. The Files editor reads it too. It isn't part of a build, so a strict error there can't fail a deploy; copy it into an older app to get the same.

With the dev server on your computer, a save now reaches it even when the sync fails (no network, the API down): the mirror in .ib/local takes your files first and syncs again on the next change. And every app's AGENTS.md now describes the dev server on your computer rather than saying there is none.

More in Getting started.