sailfork / t3code-github / apps/ mobile/ deps
- react-native-enriched-markdown-1.2.0-t3.16-29ddd424.tgz
- react-native-screens-5.0.0-t3.48.tgz
- README.md
apps/mobile/deps/README.md
The Enriched Markdown tarball comes from Julius's fork/t3-mobile branch. Its t3-fork.json records the exact source commit and upstream base. React block renderers and signed image sources (renderers, resolveImageSource) are upstream. The fork carries native streaming memory bounds (an 8 MiB measurement-key budget and coalesced pending renders), plus changes with an open upstream PR: the onLinksChange link list that link pills and iOS link menus read (#1088), Android inline image alignment (#1089), clipboard link metadata (#962), development-host autolinks (#961), and md4cFlags.preserveWindowsPaths, which keeps backslashes in Windows drive paths in prose (#1105, after md4c#5).
To replace it, commit the fork changes, run yarn install --immutable and yarn workspace react-native-enriched-markdown prepare in the fork checkout, then node scripts/pack-t3.mjs /path/to/t3code/apps/mobile/deps. Keep the package version aligned with Julius's fork/t3-mobile branch. Rename the archive to include the first eight characters of the source commit, such as react-native-enriched-markdown-1.2.0-t3.16-8d2f84a8.tgz, so each build has a distinct dependency path without version bumps. Update the tarball path in apps/mobile/package.json and pnpm-workspace.yaml's allowBuilds, and run vp i to update the lockfile. Native clients need rebuilding when this dependency changes.