Dev Blog #2 grr
Published: .
Edited on: .
Hey again, its Friday 15th September nearly 3pm. I just spent basically all day trying to figure out why the mobile and web apps were both crashing in development. First thing I tried was deleting `node_modules` (the classic), but after trying many other avenues I realised that I had only deleted the `node_modules` inside workspaces and not the root level folder. After refreshing that folder the web app worked.
For the mobile app it turned out that `tailwind` had published a new version (3.3.3) which broke `nativewind`. So pinning `tailwind` to 3.3.2 fixed this. A couple of other packages (`react-native-svg` and `react-native-reanimated`) had also gone rogue with their package versions somehow so I pinned them and everything is now fine.
Lesson learned I guess is that you can't really trust that patches and minor updates won't break things downstream, especially when you have a setup as messy as the `nativewind` etc stuff we are doing. Maybe its another argument against using `tailwind` in React Native. Also maybe should just pin packages to exact versions in future.
In other less annoying news, I decided the new focus is to trim the app down to a MVP without all the random half-baked features so I can publish to the IOS Store. So that is the focus today with lots of small changes on this effort.
Also random update - I realised the "get all users" function I was using from Clerk was capping at 10 users returned and the app actually has way more users than I realised (60+ last I looked). Not bad for zero promotion and an app that barely works... better get moving with finishing it.
Cya next time