Chad Robinson

It seems this was added and documented but never actually released?

I didn't read it thoroughly yet but at first glance they seem similar. In the comment trail there seems to be some confusion about why this is required. autoVertical isn't...

@dhoerlSA Thanks for posting this. I've tested it and confirmed it works here for the use-cases I'm using this for. Maybe change this to a PR?

I believe this is the same issue reported here https://github.com/facebook/react-native/issues/31245. I resolved it the same way reported there, by upgrading React Native to >= 0.64.2.

I got here from a Serverless project using `serverless-plugin-esbuild`. I think the documentation at https://www.prisma.io/docs/concepts/components/prisma-client/module-bundlers could use some expansion. I'm using esbuild here and I found some of the references...

@wmlutz At the top level of the serverless config, e.g. ``` ... frameworkVersion: '3', package: { individually: true, patterns: [ '!node_modules/.prisma/client/libquery_engine-*', '!node_modules/@prisma/engines/**', 'node_modules/.prisma/client/schema.prisma', // 'node_modules/.prisma/client/libquery_engine-rhel-*', ], }, provider: { ......

@aneurycasado You need to manually bundle the schema.prisma file. Since you have a monorepo and it's in a different directory Serverless is probably having trouble finding it. Maybe try adding...

Confirmed here. Anybody have any workarounds? Nothing I'm trying is working here either.

I think it's not so much "errors in the code" as it is this project's name and purpose is "prettier". More and more I'm finding it loves to turn 1-liners...

Same here. In my case sometimes it works and sometimes not. My connection is definitely initialized - I have a log entry when that happens and that's done at app-start....