Open LeoLeBras opened 2 months ago
Thank you for sharing the information. We are cautious about changing specifications because we must consider the impact on other customers already using our SDK.
I will look into a mono repo. Please let us know if you have any reasons why we should, such as background, impact, effects, opinions, etc.
Thank you for always using our products and solutions.
In my patch package, there are two things:
For the 2nd point, it's indeed important not to introduce a regression for users without monorepo. I've tested my patch package here https://github.com/star-micronics/react-native-star-io10/tree/master/example and everything works fine.
I don't know if I have an argument about whether or not to use monorepo. To be honest, in my tech team, we'd like to get away from this "monorepo" pattern/arch. But many react native packages have this monorepo support, it's become a common thing today.
👋 I've always needed to make a patch package to avoid typescript errors and installation issue (I use a mono repo) ⬇️
Would you like a PR to correct this?
My
react-native-info
:And my typescript version is 4.9.5.