examples-next-prisma-starter VS envsafe

Here's an example of testing: https://github.com/trpc/examples-next-prisma-starter/blob/ma...

{ e.preventDefault(); const $form = e.currentTarget; const values = Object.fromEntries(new FormData($form)); type Input = inferProcedureInput< AppRouter["dailyActivity"]["addDailyActivity"] >; // ^? const input: Input = { name: values.title as string, timeSpent: values.text as string, }; try { await addActivity.mutateAsync(input); $form.reset(); } catch (cause) { console.error({ cause }, "Failed to add post"); } }} > Title: Text:
{addActivity.error && (

{addActivity.error.message}

)}

)

So I am copying/learning the logic from https://github.com/trpc/examples-next-prisma-starter. In this code, there is no ID provided in the query, yet in my code, I get the error that I need to provide an ID. Since the ID in the prisma schema is cuid() doesn't that mean that is autogenerated? What am I missing?

In this quick blog post, I will use one of TRPC's examples available on GitHub to explain this concept in real life and then show you how to handle default values in development mode.

A bit of heresy to post this in the GraphQL subreddit but another alternative is tRPC + Prisma. I was testing both Pothos and tRPC yesterday and the latter is just so simple while still giving you full end-to-end type safety.

To further secure your environment variables, consider using envsafe for validation and type safety. Install the package and adjust the env/env.ts file accordingly along with the variable types:

Disclaimer: This post is inspired by env-safe by @alexdotjs and his recent Twitter reply to my thread, where he suggested handling environmental variables in Typescript with a generic schema validation library over a dedicated library. If you’re not following Alex on Twitter yet, you should definitely do it now!

In next JS it's much easier. It's not static, node can read the environment variables. For validation and type safety, you can use this.