@MarcJSchmidt@birch_js@KentonVarda I don't think I did, probably would've been better. I did this experiment over 2 years ago. Tsgo would've helped a bunch too I reckon
@MarcJSchmidt@birch_js@KentonVarda Typescript yeah. And it did just work, but required to transform the src folder using tsc, which was way slower than just stripping types like babel does in the standard RN pipeline
@birch_js@KentonVarda I used Deepkit for a RN project for exactly this purpose - checking api responses based on existing types and it's awesome that it can be done without defining schemas. But the codegen step was a hassle and I went the zod way in the end
@ChmalSzymon Also I really recommend expo to streamline working with native parts of your app. CNG is awesome. Reduces hassle to keep your app's deps to date so much. No more manual editing to install native deps. No requirement to use EAS, I just use the expo cli for prebuild
@ChmalSzymon You don't install the rn-better-dev-tools repo itself to use these dev tools, you actually use LovesWorking/react-query-external-sync, which uses the mmkvStorage property to sync the storage keys with react query, so that you can inspect them as queries.