Next.js 14 Tutorial - 28 - Parallel Routes
ฝัง
- เผยแพร่เมื่อ 25 มิ.ย. 2024
- 📘 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
Nice. I love these series. esp this episode. It makes the code cleaner and specific to route.
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.
hey !
thanks for this amazing NEXTJS14 series
thank you soo much for this amazing series, I shared with my friends as they also want to learn Next.js.
Amazing tutorials. Thanks for this amazing series…🙏👌
Great series
Amazing series ❤
Fantastic!
wow...freaking awesome
Thanks for that Sir🙏
great tutorial sir. its awesome
Thanks!
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.
Thanks
thanks man
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?
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
life saver
oh man I was trying to figure out why my components not showing ,then saw ur comments bro🙃
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?
Are there any situations to not use parallel routes? Performance or other?
Good day greetings
do we use this all the time or only that case?
Hello, how many videos will be posted with next.js 14?
I'm a bit confused about the advantages compared to the normal Components. Wouldn't creating components still allow for subnavigation or independent handling?
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?
Hi, I just have a question, doesn't parallel routes achieve a similar result an an HTML tag?
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.
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.
is @parallerl_routing page be server component??
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?
alright, the answer is in the next video :D
You should rewrite NextJS documentation
@/component please where is that coming from?
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'
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.
I think vue was better planned than react
Yes that is the real fact❤
is there any way to pass props to parallel route componet ?
Maybe from the Layout.tsx component
Can I not use the children slot and just use the other slots?
Just tested it, You can!
@@M7ilan
you can, but when error happens in one, the whole page will block instead of one slot
I am stuck here,the children slot are not rendering
same
Its not working I has done everything from reading docs to watching tutorial but its not working
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.
Me neither. I don't understand. The way I figure it, he should have access.
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.
same here, didn't work