Видео

Your appreciation made my day! I am glad i could explain the way you like! Thanks a lot

glad to hear your problem got solved!

Glad to hear your appreciation! 😀

Yes exactly!

space for optimizations maybe😀

Thankyou for your kind compliments! I think keeping yourself up to date by following blogs and tutorials and regular learning will help you create a strong foundation to be a better frontend developer.

Thankyou for your contribution! I hope this method would help lot of developers

Did you try methods in this other video? ruclips.net/video/PHlqVjuT1No/видео.htmlsi=MQX_DG7xvkfGlphg

the problem was that in nextjs 13, ui components were stored in the pages layer and these components were exported by default (export default TaskBtn etc...) and inside similar ui components, new ui architectures were exported by export const Btn (import {Btn} due what was the problem. Thanks to the idiot who wrote the code before me, now on our project every fucking button and ui component is a bitch page, which is why the build takes longer, etc. WARNING don't be like this idiot, don't write UI components in the pages layer

​@@codeek0 no, unfortunately it didn't work. thanks for the answer. i tell about problem in other comment

Glad to hear it! Thankyou😃

glad to know the video helped you! Thankyou for the motivation

Glad to hear it helped you😀!

i am glad to know it helped!

No, i am just trying to excel my fluency and pronunciation. Thanks for your warm comment though

go to the main page i.e / and about page and check the terminal in server side and there you will find the error!

@@codeek0 how to check in server side terminal please help me im a beginner...🥺

the terminal is where you have typed the command npm run dev to start the development server! There you can check the error after your page has been loaded! @@SanjayNG125

That mean the page is getting rendered in the server side. Nextjs prerenders every components in server side first and then in client side. Since window is only accessible in client side, we make a condition to check if typeof window is not undefined, which indicated that the page is getting rendered in the client side.

@@codeek0 this is obvious. But what if its ssr component and window isundefined?

​@@lenyacher8344 for Server Side Rendering, you should use the "headers" library from NextJs. It checks the header of the request from the user and then knows if the user is coming from a mobile or not. But then, if your component uses state or anything like it, you'd have to refactor to create two components: the server-side one, which uses the header's function, and the client-side one, which uses the states, and call the client-side from within the server component pass down a prop telling which kind of screen will be rendered. The problem: THIS ONLY WORKS WHEN YOU REQUEST THE PAGE TO THE SERVER. If you need your component to know the resize happened in real-time, you cannot run from the Javascript event listener and use the windows, as far as I know. OBS: I was going to do something like this, but decided to go the other way. All the knowledge is from reading the docs and trying to figure Nextjs out. If I'm wrong for any reason, please let me know.

@@codeek0any code run in useeffect will only get executed in the client so there is no need to check if the window exists because it always will

you are most welcome!

Glad to know it helped you! Your positive feedbacks are actually a motivation for me!

Thankyou daju!

You can see what is causing the error in terminal in server side!

For that you can make an organizational route and then create a layout inside this route and add not-found.js! For more you can follow this link: nextjs.org/docs/app/building-your-application/routing/route-groups

Thankyour brother!