Liam O'Boyle

> if you're confused as to why jest is included in nativewind, most of nativewind's development occurs in a jest test environment. We make changes and run the myriad of...

bump

@aleqsio @brentvatne I'd be happy to open a PR like https://github.com/expo/expo/pull/26931 to bring the mocks up to date again but I'm not sure how to regenerate them, is that documented...

Thanks; I had actually stumbled across that when looking into this but it sounds like it's targeted at module authors generating mocks for their own packages, which would presumably be...

I was unable to follow the guide earlier, but will take a look again now that we're on 53, maybe it's working again. Note that this is mitigated by https://github.com/expo/expo/pull/36839,...

Apologies for not coming back on this sooner; the missing mocks seem to have been resolved in expo/jest-expo 53 and we were able to remove the patch described in the...

> We tried an iOS build with your fork as dependency but got an error (in EAS): > > ``` > [!] No podspec found for `react-native-google-maps` in `/Users/expo/workingdir/build/node_modules/react-native-maps` >...

@salah-ghanim [it's not just react 18 vs 19](https://github.com/react-native-maps/react-native-maps/issues/5492#issuecomment-2870058185), it's different tsconfig settings; most people use [`skipLibCheck`](https://www.typescriptlang.org/tsconfig/skipLibCheck.html) so that issues like that are ignored - no fixes you make to the...

Upgrading `react-native-maps` and running into this annoying and yet easily fixable problem yet again 😮‍💨 Rebuilding a patch to suppress the `81 errors in 24 files` is a drag. Took...

Thanks @ACHP and @salah-ghanim for getting this pain point resolved - this is a proper fix for users, much appreciated.