Next.js 14 Tutorial - 28 - Parallel Routes

Рет қаралды 50,872

Күн бұрын

📘 Frontend Interview Course - learn.codevolution.dev/
💖 Support UPI - support.codevolution.dev/
💖 Support Paypal - www.paypal.me/Codevolution
💾 Github - github.com/gopinav
📱 Follow Codevolution
+ Twitter - / codevolutionweb
+ Facebook - / codevolutionweb
📫 Business - codevolution.business@gmail.com
Next.js 14
Next.js Tutorial
Next.js 14 Tutorial
Next.js Tutorial for Beginners
Parallel Routes
Parallel Routes in Next.js

Пікірлер: 55

@pmcareer109 7 ай бұрын

Nice. I love these series. esp this episode. It makes the code cleaner and specific to route.

@mdamirhossain9376 7 ай бұрын

Simple but awesome tutorials as always. I always love your videos. I bet, there might not any other video that can make this more clear to understand. Thank you.

@skanwar1351 7 ай бұрын

thank you soo much for this amazing series, I shared with my friends as they also want to learn Next.js.

@mt15explore 7 ай бұрын

hey ! thanks for this amazing NEXTJS14 series

@shalsa07 7 ай бұрын

Amazing tutorials. Thanks for this amazing series…🙏👌

@flamingosports3227 7 ай бұрын

Great series

@CKNMEDIA 7 ай бұрын

Amazing series ❤

@macdee1337 7 ай бұрын

Fantastic!

@asfandyar8088 6 ай бұрын

great tutorial sir. its awesome

@blaisekempes8659 7 ай бұрын

Thanks for that Sir🙏

@worldbest3097 7 ай бұрын

wow...freaking awesome

@tolbydamit 5 ай бұрын

Thanks!

@heyyounotyouyou3761 2 күн бұрын

Thanks, i have a usecase for parallel routes in a project I'm building.

@skanwar1351 7 ай бұрын

i appreciated your efforts and love but please Sir, consider to uploading daily classes as it could be helpful for us to learn from you sir and thank you soo much for this amazing series.

@sharpesthawk 6 ай бұрын

Hi Codeevolution, at 9:00 , could we have achieved that granular control on different parts of the layout.jsx using and instead of Parallel Routes?

@alipalvane 3 ай бұрын

thanks man

@yousuf4you 6 ай бұрын

Thanks

@AndriiShevchuk-fo8ky 7 ай бұрын

Hello, how many videos will be posted with next.js 14?

@danwsaps Ай бұрын

what if u have a dashboard data that you get from dashboard layout, and you want to share data base by segment in pararel routes?

@rishiraj2548 7 ай бұрын

Good day greetings

@ndnow12 4 ай бұрын

Are there any situations to not use parallel routes? Performance or other?

@yousuf4you 6 ай бұрын

is @parallerl_routing page be server component??

@neutralviews6 6 ай бұрын

Hi, I just have a question, doesn't parallel routes achieve a similar result an an HTML tag?

@kumar7259-b4u 17 күн бұрын

its amazing , can we please get notes of this?

@MEZOMEZO2011 Ай бұрын

I'm a bit confused about the advantages compared to the normal Components. Wouldn't creating components still allow for subnavigation or independent handling?

@algorithmscodes-9927 5 ай бұрын

I don't understand the point at 10:15 how does the url plays if we opened different routes in the slots? we switched default notifications to archived and the url changed accordingly, but then if we switch another slot, how will the url look like?

@algorithmscodes-9927 5 ай бұрын

alright, the answer is in the next video :D

@watashit5517 5 ай бұрын

do we use this all the time or only that case?

@zoethebird1 5 ай бұрын

@/component please where is that coming from?

@keithcheng8481 4 ай бұрын

The @ alias is a nextJs feature, that allows you to use relative path when importing modules. In this case, the card component comes from the components folder, so the @ shorthand replaces all the absolute path that is usually required, and trims it to just '@components/card'

@nttnhat1921 11 күн бұрын

can anyone explain why the page.tsx inside slots is not working but when i replaced by default.tsx it worked just fine

@nttnhat1921 11 күн бұрын

problem solved: i close the running terminal and re run

@StevenAdly 2 ай бұрын

is there any way to pass props to parallel route componet ?

@aurobindobhuyan2107 2 ай бұрын

Maybe from the Layout.tsx component

@M7ilan 7 ай бұрын

Can I not use the children slot and just use the other slots?

@M7ilan 7 ай бұрын

Just tested it, You can!

@algorithmscodes-9927 5 ай бұрын

@@M7ilan you can, but when error happens in one, the whole page will block instead of one slot

@xdmemeguy 5 ай бұрын

You should rewrite NextJS documentation

@you__shef 3 ай бұрын

save yourself some time and close the dev server and open it again in order to see the new slots you've created otherwise you will search for solutions to a none existing problem

@reyjanson1788 3 ай бұрын

life saver

@simple8810 Ай бұрын

oh man I was trying to figure out why my components not showing ,then saw ur comments bro🙃

@saputrauta09 Ай бұрын

Thankyou so much, this saved me. How did you know this gonna work?, i mean, why do we need to stop our dev server first?

@mkaufmandev 7 ай бұрын

As a Vue dev I feel like this isn't really showing more than one route at a time but more just using slots with the router to show multiple components at the same time. Maybe it's a semantic thing for me to understand.

@stanleyhayford6881 7 ай бұрын

I think vue was better planned than react

@tuhinjamal6221 5 ай бұрын

Yes that is the real fact❤

@cynthiaamarachi8047 Ай бұрын

I am stuck here,the children slot are not rendering

@h13q18 Ай бұрын

same

@zainn7336 4 ай бұрын

Its not working I has done everything from reading docs to watching tutorial but its not working

@SSmithYT 4 ай бұрын

Resaving the globals.css worked for me. (I removed all stuff in there outside of the @tailwind lines, saved it, repasted them all. It saved the dark mode and the new layout loaded for the complex-dashboard.

@user-un9rr8nw2u 2 ай бұрын

Me neither. I don't understand. The way I figure it, he should have access.

@user-un9rr8nw2u 2 ай бұрын

I created page, layout,@comp1,@comp2,@comp3/newPage under dash-board folder. I am accessing dash-board through routing, but accessing dash-board/newPage will not work.

@saputrauta09 Ай бұрын

same here, didn't work

@ivosrbakoski1151 4 ай бұрын

@yashwanthsekar 2 ай бұрын

I don't understand how this is still different from just using components. all the advantages that you mentioned are still available if you just components for the various section.

@chinemelumchuba-nwene1503 Ай бұрын

Yes they are still be available but maybe difficult to implement and as the application becomes more complex, it may be challenging to scale. Parallel routes in Next.js offer significant advantages when it comes to implementing features like sub-navigation, loading states, and error boundaries. With parallel routes, you can easily manage sub-navigation within these routes, allowing for a more organized and user-friendly structure. One of the key benefits is the ability to handle loading states and error boundaries seamlessly. By simply adding loading.tsx or error.tsx files within the parallel route directories, you can ensure that the application remains interactive and responsive, even when certain parts of the application are loading or encounter errors. This setup allows the rest of the application to retain its state and functionality, providing a smooth and uninterrupted user experience. For example, if one parallel route is loading data, the presence of a loading.tsx file in that route can display a loading indicator without affecting other routes. Similarly, an error.tsx file can catch and display errors specific to that route, ensuring that other parts of the application continue to operate normally. This isolation of states and errors makes managing complex applications more straightforward and robust.