Dries Cruyskens

[Dries Cruyskens @DCruyskens]

@dinwwwh This is great! We just split our nextjs routes and orpc client to achieve something similar in orpc v1. Our nextjs dev performance improved dramatically. Glad to see v2 will support this natively. Looking forward to stable!

[Dries Cruyskens @DCruyskens]

@acdlite @aurorascharff The only thing missing is a way to group staged changes like jetbrains's changelists

[Dries Cruyskens @DCruyskens]

@yoboigouda @michael_rispoli @tannerlinsley @nextjs Just import types from payload-types.ts

[Dries Cruyskens @DCruyskens]

@michael_rispoli @tannerlinsley @nextjs Same boat. Been slowly refactoring away from server actions & components to tstack query and orpc so I can switch to RR/start and run a different server for the Payload instance. E2e types & local API should not be affected. I'll just have 2 deployments on Vercel from then on.

[Dries Cruyskens @DCruyskens]

@thdxr @sotoksotok This would be very helpful, I was surprised to see a tunnel is not opened by default when running sst deploy. Next build would benefit from it so it can reach the database for ssg.

[Dries Cruyskens @DCruyskens]

@theo What's the best way to run Drizzle migrations when Vercel deploys a Nextjs app? I find it strange there is no mention of this in the docs. Usually I'd run migrations first and block deployment when they fail.

[Dries Cruyskens @DCruyskens]

@chris_mccord Brew automatically runs `brew upgrade` before some commands. These are just formulas that are already installed on the system. You can disable it by setting this environment variable first: `HOMEBREW_NO_AUTO_UPDATE=1`