Christopher Ehrlich

also dont merge before arabic is removed from the list of known languages, otherwise we're deploying two fake arabic pages

@juliusmarminge lmk when you're ready to merge and i'll remove the arabic placeholder stuff (or feel free to remove it yourself)

> Upgrade `next-auth` -> **4.18.x** resolves this issue. I don't think it does. Based on my understanding (outlined above) this issue is fundamental to how we have chosen to implement...

> I'm finding the same thing happening with prisma, using sqlite. It may be related to the changes to unstable_getServerSession in next-auth 4.18. Could you pin next-auth to 4.17, reinstall...

next-auth has been temporarily pinned to 4.17, and we'll have a better solution asap. @murdoch those CLI warnings have always been there with `unstable_getServerSession`. you can follow the links in...

if anyone has this error with an existing t3 app using next-auth 4.18, here is a fix: https://github.com/t3-oss/create-t3-app/pull/932/files#diff-45898f28661180eaf9cfdf9a99f4949f0ef7c76ea915c85455ac5409f4ee73bf

spacing looks good! does it maybe make sense to force this section to be ltr?

The reason for the 767 value is that the breakpoint is at 768, so we want this behaviour until 1 pixel before that. Was this PR in response to a...

> Create.T3.App.-.Brave.2022-11-19.17-08-11.mp4 what you are showing here seems like the correct behaviour - the menu exists until 767 px, and doesn't exist at 768+ px because then the "Docs" etc...

> In case this helps anyone, you can use the documented Next.js setup (for the pages router) as-is with an app router based app, by exporting the provider from a...