Vercel needs to watch this video and improve the DX here for sure
@tiktalk45734 ай бұрын
seems very DX friendly to me!
@huyifan83Ай бұрын
Or we can switch to Remix
@jessyndaya94878 ай бұрын
It's too much for nothing my friend 😅
@albin61263 ай бұрын
this all started for just solving the issue of having a separate loading file for each component is silly. If that is the only benefit of this. Then this is an overkill
@codiumytАй бұрын
@@albin6126 This was a lifesaver for me though. I have a header in my layout that I need to renders different things in depending on the route. This way, I can pass in the parallel route component into my Header from each subroute and have them all server rendered (mainly because I can't access full route path in layout.tsx).
@noeljose3 ай бұрын
in the last 4 years, this man helped me go through most of the challenges i face as as self thought programmer. Today I work for an MNC and 30%-40% of the code solutions Implemented, I learnt from WDS.
@adammilner45128 ай бұрын
this looks horrifying, so much overhead even in this super simple example
@untalentedwebdev8 ай бұрын
exactly my thots
@tiktalk45734 ай бұрын
I don't agree
@huyifan83Ай бұрын
Next.js is going to a wrong way. It creates a lot of overhead unneccessariely
@bernardoolisan1010Ай бұрын
I consider it would be easier to use middleware
@sujjee8 ай бұрын
Thank you for explaining parallel routes in such a simple and easily understandable way. By the way, could you also explain Drizzle the way you explained Prisma in one hour?
@marcialabrahantes33697 ай бұрын
drizzle is most like SQL. you can learn SQL and it'll transfer over pretty seamlessly
@tom.watkins8 ай бұрын
The main benefit of this is being able to use the loading and error pages within each parallel route i am guessing. For most cases its fine to just import the server components, you hust have to remember to put your own suspense/error boundaries around them
@chrtravels7 ай бұрын
I was wondering why this would be necessary when you could just import server components. This makes sense though. I could see the benefit of having the separate loading and error pages. I am not very familiar with using suspense/error boundaries, so that is something I need to delve into.
@tom.watkins7 ай бұрын
@@chrtravels loading and error pages are just a nice abstraction over having to put in your own suspense and error boundaries so it's a nice DX improvement for people less comfortable using them. That being said, it's worth knowing how to use them yourself as Suspense in particular is usefulfor other things in react, things like lazy imports and the new 'use' hook with promises as props both work very nicely with Suspense
@theisoj8 ай бұрын
Great video! Thanks Kyle as always! 👍
@havokgames82975 ай бұрын
This video did a good job of _how_ these works. But I really can't tell the _why_, because the examples are so generic. Is this useful for a multi-panel layout where you navigate within the panels separately? Maybe something like a playlist + music player?
@ddrweb_8 ай бұрын
Hi, thanks for the video. I have a question tho, If I create a route with parallel routes, why do I need to declare/create the parallel routes for my nested pages, maybe I want them just for the main parent , feels a bit weird :|
@whoman79308 ай бұрын
Yeah, that's really odd. I always have to add a default page that returns null to counter that. 🥲
@aldhyx3 ай бұрын
Agree, I can use it to load analytics components separately but have to put default page to encounter that issue
@nemeziz_prime8 ай бұрын
Can you also do a simple video on subdomain routing in React/Next.js?
@kellingtoncrivelaro39298 ай бұрын
Would love It too
@VinayTandale8 ай бұрын
Its being complicated day by day easier the simpler the better
@otn9878 ай бұрын
The conditional rendering works the same way using parallel routes or not with slightly different syntax. if(!isLoggedIn) return Vs. if(!isLoggedIn) return login. Am I missing something?
@hexantra2 ай бұрын
i thought so, but i think pararrel routing can be utilize if you are in server component
@mohammadahmermalick78698 ай бұрын
Thanks you bro! I love your channel ❤️ You are doing a great job 👍
@milan51318 ай бұрын
3:37 react has type for ts that makes it simpler to define types where u want to use children so you don't need to define type for children: PropsWithChildren
@rrAzz2 ай бұрын
This feature is good for a dashboard with a lot of graphs that can take a while to load the data needed to render the graphs
@sanchayan.bhunia3 ай бұрын
You know what! I really love your intro slogan.
@BugsNRoses_8 ай бұрын
happy new year kyle❤
@theavazov8 ай бұрын
Great video Kyle, can you make a video about i18 in app routes?
@alirezak58705 ай бұрын
even if you use middle wares and auth packages on this feature you get in trouble more because slots children or any props you are passing in your layout don't work as you expected. and your route system completely make parallel bugs.
@hexantra27 күн бұрын
and the worst part is the bug when in development, and the behaviour become more unpredictable
@wchorski8 ай бұрын
would love a talk on how to create a template app that is shared between multiple clients. With tips on how to handle 1. unique assets 2. customer side configuration 3. adding and pushing updates across all instances of this app
@fx-ry5iu2 ай бұрын
Hi Kyle, what about creating advanced JS / TS / React course ?
@mahadevovnl8 ай бұрын
You can change the indentation of your file tree on the left in VSCode, could you please do that? The default 2px indentation is horrible and makes it hard to see what folder is inside what folder.
@naufalnasrullah69658 ай бұрын
7:29 insert a login page inside of dashboard isn't good idea, it should have its route alone
@shawnxiong20116 ай бұрын
This nextjs dark magic is overcooked
@chrtravels7 ай бұрын
The docs aren't clear but it sounds like the parallel route has to be a server component. I have a PostList server component, that I could turn into a parallel route, however I have a PostCard, which is imported into the PostList. The PostCart is a client component. So I would not be able to use the Parallel routing on the cards themselves? It's the cards that I would want to have the loading state on.
@anhvuuc86938 ай бұрын
This still easy, Intercepting Routes is an headache :D Hope you can have a video for it
@code_react8 ай бұрын
WOW. this is amazing to learn.
@nkululekomthimkulu12488 ай бұрын
Looks cool. I'll try it out.
@Henrique010108 ай бұрын
You did an amazing job explaining this. It looks like a clever way to place multiple server components in a single page, until it doesnt. It gets annoying really fast with the nested files and development mode gets super buggy. I cant believe Next is releasing this, the framework was once an example of great DX...
@movoyemickele8 ай бұрын
Hey Kyle, I'm curious if there's a method to eliminate the loading time experienced when navigating between pages in NextJS. I'm aiming to develop a Progressive Web App, but I've noticed that NextJS fetches each page from the server based on the URL, leading to some delay. This contrasts with React Router, where page transitions are nearly instantaneous since it doesn't require fetching the new page for every navigation. Is there a workaround or solution for this in NextJS? I almost think NextJS sucks for PWA.
@vivekkaushik95088 ай бұрын
PWA and SSR doesn't make sense. In order for an app to be PWA you've to make the app CSR so that client can download the entire app and run it offline
@movoyemickele8 ай бұрын
@@vivekkaushik9508 Do you have any insights on implementing this in NextJS? Simply specifying 'use client' doesn't work, as the app's router is designed to deliver individual pages for each specified URL. I'm looking to enable the user to download the entire app, similar to the experience with plain React where the user downloads the entire app. Any suggestions?
@twothreeoneoneseventwoonefour58 ай бұрын
@@movoyemickele why are you even using nextjs then. That's like buying a car to go to a store 100m from your home. Use Vite instead for your purposes.
@jaspreetmaan1218 ай бұрын
@@movoyemickele if you don't use ssr, don't use next js
@acousticmunda64008 ай бұрын
@@movoyemickele just use "use client" in the parent layout file
4 ай бұрын
Next.js just amazing
@a_m___s_y8 ай бұрын
Parallel routing is powerful, but it's absolutely annoying when use it in development mode. Go through the document many times and finally find out the issue only exist in development mode from your video... thanks for your video
@KnaveKaiser8 ай бұрын
thank you for the great video. can you make a video demystifying internationalization in the next js 13 using app router? I'm having a hard time setting it up in a way where the default locale does not pollute the url. thanks again.
@carlosbotero19478 ай бұрын
There is a really cool library called "next-roots" that have a great i18n solution .
@dreamsachiever2128 ай бұрын
+1
@boglegogle8 ай бұрын
Using i18Next, super easy to set up and works great. The default locale doesn't show up in the route and next handles all routing for you so if you never have to specify locale routes, it just does it
@firewatermoonsun7 ай бұрын
What if I don't want User Settings and Article Settings but just want /dashboard/settings with Settings folder?
@albin61263 ай бұрын
use default and add nothing in it
@Slaat17 ай бұрын
10:40 thank you for touching on this! It's a shame this is so buggy in dev
@bayuputraefendi47178 ай бұрын
Thanks, now i can improve my code
@WayneHuang-e5c4 ай бұрын
Anyone know if it's possible to have a wrapper layout or page to pass in props to the slots? The use case if there was interactivity outside of the parallel routes that can show/hide a particular slot from a button click.
@gamemak0rАй бұрын
I couldn't really understand the point of parallel routes over components as they already are until 9min into this video, with the advanced nested parallel routes... but then to see it doesn't work in dev mode?... Having to restart the dev server for it to work can make the problem really obscure.
@lcarv208 ай бұрын
The dx looks awful. Having to restart the dev server frequently is annoying, not to mention the dev glitches that I have already spent hours trying to fix thinking it was a problem with my code.
@faizsyed6588 ай бұрын
True. Classic front end bloat
@ParasBansal10Ай бұрын
IMO, Vercel took this simple concept and made it 10x more complex.
@abubakar.khawaja5 ай бұрын
sounds like a video for "why you shouldn't use Parallel routes in Next.js"
@rxnniiee3 ай бұрын
how does this differ from components? why is this a thing if you could do the same thing by conditionally rendering components that do the same thing?
@OlehKopyl7 ай бұрын
I did not understand a thing. Isn't it true that a route sits on a separate url? 1. Why do you render everything on one page? 2, How is it possible to have a parallel routes if a route is always loaded one at a time. If you have 2 route on the same route, ut's just a plain component, not?
@Daddyjs8 ай бұрын
You are a Next js GOD
@MrAlao6758 ай бұрын
One of the turn offs here is restarting dev server. Well I don't have a use for the complicated parallel routing for now😊
@saudalghamdi56088 ай бұрын
Hi Kyle, when are you going to launch the Next.js course? I'm thinking about learning Next.js and there is no better teacher in the JavaScript world than you!
@TabuHana8 ай бұрын
Its in the description
@WebDevSimplified8 ай бұрын
It will most likely be this month
@griffadev8 ай бұрын
Tried using this feature and had to back it out because its so unstable (for the more advanced uses ) the fact it's so buggy in the tutorial only proves this
@planesrift8 ай бұрын
Top notch developer experience.
@jacobphillips92358 ай бұрын
Thanks!
@WebDevSimplified7 ай бұрын
You're welcome! I am glad you enjoyed the video.
@raphaelpicard89818 ай бұрын
Hello, I wanted to know if with your videos there is the possibility to put subtitles in French?
@bernardoolisan1010Ай бұрын
Why not using middleware for this?
@TeaBroski8 ай бұрын
Like this if you appreciate Kyle's content but need to 1.5x to not follow asleep
@dextrox26987 ай бұрын
This feature may seems useless to some ppl but along the line it comes to tackle some problems i.e intercepting routine
@aravind.a8 ай бұрын
what is the advantage of this? We can also use swr to load each content on page.
@RadianRasyid7 ай бұрын
i dont't know im not able to use parallel route just like how you do it. it worked for the root layout, but not for the nested route. i'm using nextjs version 14.1. maybe a little help?
@DoItWithADance8 ай бұрын
What a complete mess, I fail to see how this is simplifying my app code except bloating it. Perhaps it has uses in larger app code bases?
@unajujupiter67256 ай бұрын
unable apply conditional routes to home page, i guess the layout for home page is RootLayout which is a little bit different, anyone have done it before? just wondering.
@ikbo8 ай бұрын
Why does the course say "next.js coming soon"? Has it not been released yet?
@username2206-c8j5 ай бұрын
thank you !!!
@elephant_8888 ай бұрын
Way too many abstractions. This makes me so happy I’m learning HTMX!! We’ve really gone crazy with the frontend frameworks. 😅
@DavidSmith-ef4eh8 ай бұрын
Crazy. I wanted to switch my teams project to the new app dir structure, but I guess we'll just stay with pages forever.
@DaviAreias8 ай бұрын
I started using nextjs on my journey but then changed to rust+ vite on the frontend and reduce ram usage from 100~120 MB to less than 10MB, that was before the newer nextjs versions btw
@DavidSmith-ef4eh8 ай бұрын
@@DaviAreias learning rust as well, but doubt i will push it in my company. It just makes no sense for them, since the bottleneck are the connection speeds and our database. but I will certainly use it for my own project. Don't know about vue though, react has a great ecosystem.
@0xAndy8 ай бұрын
Thoughts on Parallel Routing in Next 👎 too much boilerplate 👎too buggy in dev (barely usable at times) 👎not ready for prod. Next should improve the DX immediately before pushing this further
@DavidSmith-ef4eh8 ай бұрын
Just look how many files he had to create. And we all know that creating files is the slowest part of developing :D
@البراءبنمالك-ر1م8 ай бұрын
You can name pages components with different names other than just "Page"?!
@donaldpetervicente83518 ай бұрын
Hi Kyle how do you do the shortcut to instantly imported the red tagging(error)(wait) that is not manually imported? what is the shortcut key? Thanks in advance.
@debopamgupta8 ай бұрын
Ctrl + . Will bring up the code actions in vscode which has many options, here you have the option to auto import the function
@donaldpetervicente83518 ай бұрын
@@debopamgupta Many thanks bro!😁
@ccccssss-df8 ай бұрын
Thank you for the explanation on parallel routes. However, I was wondering if you could possibly show me what the code in the 'wait' function, which is located in the 'lib' folder, looks like? I would appreciate your help.
@BradenKelley8 ай бұрын
probably just something like `const wait = (ms: number) => new Promise(resolve => setTimeout(resolve, ms))`
@ccccssss-df8 ай бұрын
@@BradenKelley Your answer helped me understand it better. I appreciate your assistance.
@DannyBLV8 ай бұрын
all these issues in dev mode doesn't worry anyone here ?
@Slaat17 ай бұрын
6:41 I know you wanted to give a good example but this isn't one, authentication should be handled in the middleware. you could have checked for user role and displayed different components
@kenshinhimura31408 ай бұрын
I mean that the component folder in react is dead because now every pages have his folder component.
@Dylan_thebrand_slayer_Mulveiny8 ай бұрын
2:00 why would they inject HTML into the suspense component as a property. Shouldn't that be a slot instead? That seems incredibly bad to me. I can't possibly think of a legitimate reason to do it that way.
@thomasmiller14068 ай бұрын
Cool, would be nice if there was away to define common children compents like loading and error. Personally i prefer this over being verbose but not going to lie running in dev mode looked absolutely horrendous!
@IvanLopes-k9z8 ай бұрын
Can you make a video on how to create 2 diferent set of pages with same names but for mobile and for desktop so we don't need to have code mixed can have 2 diferent routing and as a plus if theres a way to make url only show main donain feven being in pages like maindomain/blog but i just see maindomain I was trying to do sometihng likes this App [...mobile] to catch all mobile (mobile) to group all mobile and create an invisible /mobile page.tsx store page.tsx page.tsx layout.tsx inside layout my idea was create an const isMobile = window.innerWidth
@ahmadmuqadas787 ай бұрын
i love your hiar bro
@rodrigocremella8 ай бұрын
Great video. But I decided to skip Next JS only because the server error on each render/code change 🤧
@bpaintx28 ай бұрын
Sounds like a code problem, not a Next JS problem ;)
@boglegogle8 ай бұрын
That means you have an error... Next js hot loading works just fine
@ionutsandu59138 ай бұрын
How is this a benefit over just creating components and conditionally render them?
@Rkdo_Dev7 ай бұрын
in this point of time, nothing.
@hanesmitter14694 ай бұрын
Though NextJS makes me give weird names to my files...I like weird names better within JS code in strings
@hellokevin_1338 ай бұрын
I respect you and appreciate the work you put into your courses, but given the quality of the recent React & Next docs, I think it'd be silly to take a course or look elsewhere for learning these technologies.
@ts37988 ай бұрын
No offense, but this is a stupid comment. A lot of people prefer to learn by watching videos.
@GermansEagle8 ай бұрын
I disagree. The documentation says how things are. The course is using it in a professional manner. There was docs on react hooks, but his course changed how to actually use them.
@yashyadav51168 ай бұрын
learn by doing
@N8X4TE8 ай бұрын
What is a good use case for this?
@DavidSmith-ef4eh8 ай бұрын
Making developers switch to vue or svelte, I guess...
@N8X4TE8 ай бұрын
@@DavidSmith-ef4eh fr
@berniko49547 ай бұрын
@@DavidSmith-ef4eh lol thats why I switched to sveltekit, but then switched back after a month because uk,I do not want to be a broke
@Holykael18 ай бұрын
This feature is completely useless. Why create users and articles as "parallel routes" when you can just import the components into the dashboard and render them there
@hardcorecode8 ай бұрын
I have been asking myself this exact question.
@ShantanuAryan678 ай бұрын
probably useful with shallow routing. layout components wont remount, data wont be refetched
@neociber248 ай бұрын
In NextJS app-dir each route can have it's own loading, error pages, this feature allow you to separate the logic. Also share the layouts.
@Holykael18 ай бұрын
@@neociber24 what's stopping you from defining those components in their own files and just importing. No need for any special feature
@k4f8 ай бұрын
Agreed. This is some over engneered bs. And buggy as hell
@yashyadav51168 ай бұрын
parallel routing
@DavidSmith-ef4eh8 ай бұрын
Great. I always wanted to restart my env after a change. Nextjs is really pushing things further...
@Niksorus8 ай бұрын
Hot damn, yet another way to do the exact same thing 🤣
@justafreak15able8 ай бұрын
Bro just rediscovered Components 😂
@ОлегБаранчиков-ф5у8 ай бұрын
NEED MORE FILES
@thecoder163122 күн бұрын
What's horrifying to see is how people realying only on video insted of their offical documentation - video explained everything well and it was easy to grasp but you still gotta read the docs so you know more about it. Parallel routing definitely has its uses if you're building some complex dashboard . Like the most of questions you guys are asking would literally start making sense if you just read the docs once lol.
@Goofy89075 ай бұрын
Is the purpose of this to increase app performance or just to improve the dev experience?
@kerovinvillegas64028 ай бұрын
Im not really fan of this feature. Just dont overthink things. You can create this "parallel" with simple container component with less complicated pre-requirements.
@cqz894 ай бұрын
App routers will add extra json at the end of your html, double page size, the response time is slower than page router.
@jatul288 ай бұрын
Why it's so much overly complex
@InsidiousGT7 ай бұрын
This looked cool until the advanced routing section. DX took a nosedive at that point, should've left the feature off until the DX is baked
@valehisma4 ай бұрын
thanks for the video. this feature doesn’t make any sense. why complicate it when you can just import components? Also, you can pass props easily if you have any
@ruanxun94545 ай бұрын
Anyone having a real life use case using parallel routes?
@albin61263 ай бұрын
this all started for just solving the issue of having a separate loading file for each component is silly. If that is the only benefit of this. Then this is an overkill
@avijitchanda79448 ай бұрын
I don't find anything good in this use case also don't know what next js trying to do 😅😅😅 I love pages even more
@rahilansari2618 ай бұрын
Why can't we just render components rather creating parallel route
@コンデンサー4 ай бұрын
イケメン
@amined8018 ай бұрын
this is nice, but i think it's better to go with Laravel (Laravel ecosystem provide you everything you need depends on your project) instead of try to learn every next js new feature which maybe will change in future again haha
@bpaintx28 ай бұрын
So Laravel never updates?
@amined8018 ай бұрын
@@bpaintx2 they do but they don't change everything
@rishiraj25488 ай бұрын
🙏👍
@penyintastoxic8 ай бұрын
I still dont understand how this feature will useful for my project