You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deploying T3 app to Vercel using the Zod generator, the install command runs indefinitely, most likely because Vercel cannot find the npx zod-prisma-types command as a valid command. However, it doesn't crash for some reason until the default Vercel timeout occurs and closes it.
Screenshots
To reproduce
Create a NextJS aplication using create-t3-app t3-app
Provide it with minimal confuguration adding prisma
Add the generator using using any pakage manager npm i zod-prisma-types
Add the generator to the schema like below
Upload the project to vercel
generatorzod {provider="npxzod-prisma-types"}
Fix
generatorzod {provider="zod-prisma-types"}
Package versions (please complete the following information):
zod: 3.22.4
prisma: 5.1.1
next: 14.0.3
Note
While it's unclear if this behavior stems from a misuse on my end, for the benefit of others encountering this issue, there should ideally be a flag or documentation update within the usage section to address this.
--
The text was updated successfully, but these errors were encountered:
julio-ccatb
changed the title
Infinite Execution in Vercel Installation Command with Zod Generator [BUG]
Infinite Execution in Vercel Installation Command with Zod Generator
Nov 28, 2023
julio-ccatb
changed the title
Infinite Execution in Vercel Installation Command with Zod Generator
Infinite Execution in Vercel Installation Command with Zod Generator [BUG]
Nov 28, 2023
When deploying T3 app to Vercel using the Zod generator, the
install
command runs indefinitely, most likely because Vercel cannot find thenpx zod-prisma-types
command as a valid command. However, it doesn't crash for some reason until the default Vercel timeout occurs and closes it.Screenshots
To reproduce
create-t3-app t3-app
prisma
npm i zod-prisma-types
Fix
Package versions (please complete the following information):
Note
While it's unclear if this behavior stems from a misuse on my end, for the benefit of others encountering this issue, there should ideally be a flag or documentation update within the usage section to address this.
--
The text was updated successfully, but these errors were encountered: