Комментарии:
can you please talk about prerender error on nextjs 13? i am having this error on my cart folder which consists of components and 1 page.tsx file
ОтветитьThanks, I'm struggled at ErrorBoundary at first, no idea that nextjs handle it automatically. 😂
ОтветитьThank you, great video! Wouldn`it be easier to just put all the Auth error code on the error.ts page? Use session and show message since every error redirects to error page instead of putting AuthRequiredError on every page? Like: {!session && 'Please log in if you want to continue'}
ОтветитьCan this also be implemented in a pages router? If not, i would consider migrating to app router just for this
ОтветитьThank you Josh- Big fan of you-. I went in depth with documentation and I just confused between expected and unexpted exceptions. Based on the documentation, this file is used for unexpected errors during the runtime. LIke network interruption, ... and we use this file to display human friendly errors to the users with the ability to recover the situation ( recovered network ) instead of refresh the page. While we can track the errors using error reporting service like sentry. Correct me if I'm wrong?
Ответитьi dont know why but nextjs returns 200 status code when error occurs, why not 503?
ОтветитьI don't think that's the right way to use error.js, because the documentation says "An error file defines an error UI boundary for a route segment. It is useful for catching unexpected errors that occur in Server Components and Client Components and displaying a fallback UI." where the word "unexpected" is specially bolded. That explains why we actually can't use custom error classes - the name of the caught error will always be "Error" (as one other guy pointed out in the comments) and we won't be able to get any custom props.
ОтветитьHow to remove left-bottom error notation button from nextjs default error?
ОтветитьHow do i send error with status code from api?
Ответить-1
I used google as an auth provider with nextjs and i deplyed the app but receive There is a problem with the server configuration. Check the server logs for more information. nextjs
can you share mote about handle "Error: Hydration failed because the initial UI does not match what was rendered on the server. " ?
Ответитьthis was awesome
ОтветитьHey josh , how could yo remove the red box with the warning of error? everytime that i click there it show a part of my code
where the exception was throwed
does this work via the catch error when fetching data?
ОтветитьThank you my friend very nice content
ОтветитьCan I ask what snippets do you use?
ОтветитьNice!
What about production error messages?
They are often hidden to ensure that no sensitive data is leaked.
How can we deal with this to know exactly which exceptions were thrown?
Dude this makes me so happy! Thank you for caring ❤
ОтветитьJosh keep tried coding
Ответитьthis is sweet thank you. would love to have those error messages in a toast notification... time to experiment
Ответитьcan i use next 13 app directory with trpc?
Ответитьthank you so mush bro
ОтветитьCan you tell us how can we access req object/context/headers in app directory that we accessed before using getServerSideProps in Next.Js
ОтветитьThank you for your content!
ОтветитьJosh, would you mind sharing your snippets extension? I find it very convenient for ts components
Ответитьyou are amazing Josh. Thank You
ОтветитьThank you
ОтветитьHey josh, what do you prefer new app directory or pages directory for new projects? I was using remix run its is also great
Ответить