Dan Romero
@dwr.eth
Post-Warpcast announcement AMA!
29 replies
0 recast
0 reaction
Alex Loukissas 🍉
@futureartist
Are you sticking with RN for mobile apps?
1 reply
0 recast
0 reaction
Dan Romero
@dwr.eth
Yes. All of the clients — mobile, desktop and now web are in a monorepo architected by the one and only @nickcherry
4 replies
0 recast
0 reaction
Alex Loukissas 🍉
@futureartist
@nickcherry what are you guys using for monorepo mgmt? I’m evaluating turborepo and nx for ours.
1 reply
0 recast
0 reaction
Nick Cherry
@nickcherry
We are (in theory) set up for Turborepo, but we aren't really leveraging it at the moment. So essentially we're just using Yarn workspaces, at least for desktop + web + pure Javascript packages (e.g. our data-fetching and hooks modules). The mobile app (and cryptography libs) also live in the monorepo,
2 replies
0 recast
0 reaction
Nick Cherry
@nickcherry
but due to the quirks of React Native (notably that the Metro bundler doesn't support symlinks), I could not for the life of me get it to work, at least not with the desired DX (e.g. fast refresh on file change). To get to that point, we're using a janky home-grown solution based on Yalc.
1 reply
0 recast
0 reaction
Nick Cherry
@nickcherry
Basically, if you're working within a package (e.g. our api client) and want live updates in your mobile app, you kick off a `yarn watch` command that watches for changes in relevant files, rebuilds the package + copies it to a folder within the mobile app that we target in package.json.
1 reply
0 recast
0 reaction
Nick Cherry
@nickcherry
It's possible there's a better way. IMO having all the apps live in a monorepo where they can easily share code + you can get immediate feedback on breaking changes before they're merged is worth the trouble. But wrt RN, there be dragons
0 reply
0 recast
0 reaction
