Client-side Exception Occurred
What's the best way of handling this (nextjs client-side exception)? I've already checked the docs and it recommends error boundaries, which i do understand the reasoning but it's not what i'm looking for
If i understand error boundaries correctly, they will render something completely different when you get this client-side errors, what i want however is for the client to render just as is despite the error, 99% of the time anyway, i get these kinds of errors when I try to get a property and it doesn't exist / is null / undefined, in that case, i don't want the entire app to crash, i simply want it to not render whatever is missing
So how do i do this?, i.e. just ignore the error and if things are undefined them let them be undefined...
App Router and Page Router
Hey everyone, I'm new to T3 stack. Just had some confusion on the initial setup. I see next has both app router and page router, with app router seemingly the path they are investing towards in the future. I'm curious when I created my t3-app. I have an app and pages folder. My understanding was that you either have one or the other depending on whether you are using app router or page router.
Looking at the T3 docs, there's also a section on Folder Structure (Pages) and Folder Structure (App) https://create.t3.gg/en/folder-structure-pages. Ideally I want to use app router, would anyone be able to explain what's happening in my setup since I have both?...
