Amir Hossein Shekari
Amir Hossein Shekari
Yep, what you are saying is totally correct, but sometimes we are dealing with external APIs that we have no control over. having a library that lets me customize the...
@mrousavy can you please mention in README that your library doesn't have support for android? if so
Hi @nurul3101, This error is causing a problem in SST deployment, here is the stack trace ```json "stackTrace": [ "PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime...
Hi @natew I believe this library is not maintained anymore, i just tested the [Dripsy](https://github.com/nandorojo/dripsy/issues/308) myself, and it's extremely faster than before (556.16 to 125)
> The versions mentioned in the issue for the following packages differ from the latest versions on npm: > > * `@react-navigation/native` (found: `6.0.14`, latest: `6.1.2`) > * `@react-navigation/stack` (found:...
I found a possible solution, here: https://github.com/react-navigation/react-navigation/issues/10317#issuecomment-1402343309
Hey @jayair Maybe I am making a mistake, but is the console auto runner using the app's local SST version, or a globally installed version in the console?
Hey, @jayair, I think it might be a mistake on my end, but as soon as I upgrade to the new SST 3.11, the console stops working for me even...
It's related to the metro bundles starting late, run the app in production mode and you will receive the even just fine