Christopher Ehrlich

> Good feedback @c-ehrlich > > > Regarding the navbar of the first example: What would the search box do? Like what would it be searching? I think the search...

I like the idea of this as I think many users are probably just ignoring the typesafe env vars and using process.env instead because that's what they're used to. This...

Can confirm this works, not sure I was doing wrong earlier. Looks great. Do you want to open a PR for it? I think it should be reviewed by as...

Another downside I can see is that you get autocomplete on all env variables everywhere, even though they don't exist everywhere (ie non-`NEXT_PUBLIC` in the frontend). This is a nice...

Nitpicking, but imo > The best way to setup an > opinionated, full-stack, typesafe > Next.js project works better even though the last line is shorter than the others

yes, seems to be some change in the typedef ``` ./src/pages/_app.tsx:13:16 Type error: Property 'session' does not exist on type '{}'. 11 | const MyApp: AppType = ({ 12 |...

12.2: ```ts export declare type AppInitialProps = { pageProps: any; }; export declare type AppPropsType = AppInitialProps & { Component: NextComponentType; router: R; __N_SSG?: boolean; __N_SSP?: boolean; __N_RSC?: boolean; };...

> @juliusmarminge do I need to translate the frontmatter too or will it cause some issues. We have a guide for translations now: https://github.com/t3-oss/create-t3-app/blob/next/www/TRANSLATIONS.md It's probably still a bit rough...

I see you've started working on this :) Closing the issues now, feel free to reopen if there's something important.

``` [04:52:26.390] 1. If present, be sure your `build` script in "package.json" calls `next build`. 2. Navigate to your project's settings in the Vercel dashboard, and verify that the "Build...