Learn Next.js Parallel Routes In 16 Minutes

Hot damn, yet another way to do the exact same thing 🤣

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

Top notch developer experience.

You can name pages components with different names other than just "Page"?!

The conditional rendering works the same way using parallel routes or not with slightly different syntax. if(!isLoggedIn) return <LoginPage> Vs. if(!isLoggedIn) return login. Am I missing something?

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.

So much complexity noise from the technology itself, looks so clunky to use

I don’t think it’s useful as we’re already gonna have each route for each feature

Next.js is getting out of hand. Formerly you could use code from your create-react-app SPA or client side rendered page, create a few files in the pages directory and call it a day. Now they want you to create millions of files, folders, subfolders. Never going to use app way. If they ditch pages, I'll replace the framework.

Great. I always wanted to restart my env after a change. Nextjs is really pushing things further...

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

This still easy, Intercepting Routes is an headache :D Hope you can have a video for it

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

now finally i can stop learning Next.js.

One of the turn offs here is restarting dev server.
Well I don't have a use for the complicated parallel routing for now😊

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?

Can you also do a simple video on subdomain routing in React/Next.js?

Way too many abstractions. This makes me so happy I’m learning HTMX!! We’ve really gone crazy with the frontend frameworks. 😅

WOW. this is amazing to learn.

Great video Kyle, can you make a video about i18 in app routes?

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

Great video. But I decided to skip Next JS only because the server error on each render/code change 🤧

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.

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

Useless feature
It’s generating more complexity then just importing components
For video thanks a lot

create your own wait function and ditch the lib
function sleep(milliseconds) {
const start = new Date().getTime();
while (new Date().getTime() - start < milliseconds);
}

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!

another "stable" feature of app router...

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.

Happy 2024

this looks horrifying, so much overhead even in this super simple example

What is a good use case for this?

I mean that the component folder in react is dead because now every pages have his folder component.

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.

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.

Why it's so much overly complex

Its being complicated day by day easier the simpler the better

happy new year kyle❤

Its better to use vanilla react with react router and vite then using buggy and slow nextjs.

Such a cool feature, I love this!

Looks cool. I'll try it out.

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

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.

When your NextJS course releasing.

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 :|

It's too much for nothing my friend 😅