Amir Hossein Shekari

look like they don't maintain this boilerplate anymore I updated the packages myself, thinking about creating a fork of this wonderful boilerplate with upgraded packages. also, some of the packages...

> @vanenshi Can you share your upgraded version, please? yeah sure, I'm going to open a PR and add the most recent version of packages. ill notify you then

> @vanenshi were you able to fork and create this boiler plate with upgraded packages? If so can you please share it here? Actully i am not using this poilerplate...

> Got it! I'll see if I can work on that and make a PR any progress yet?

Thanks guys

take a look at the https://docs.nestjs.com/recipes/prisma I was planning to create a fork of your boilerplate with `prisma` https://www.prisma.io/docs/concepts/more/comparisons/prisma-and-typeorm

@JustDenP Thanks denis I guess I'll try mikroOrm

Looking forward to this. I also open an issue on the react-i18next that might solve the problem by customizing the `nsSeprator` on the typescript side: https://github.com/i18next/react-i18next/issues/1467

I manage to resolve it by providing the correct `android_keyboardInputMode`

`react-native-reanimated` had this problem once, they seems to fixed it in next version https://github.com/software-mansion/react-native-reanimated/issues/3523 maybe we can use their approach to fix this