Next.js App Router: Routing, Data Fetching, Caching
HTML-код
- Опубликовано: 20 июн 2024
- @leerob, VP of Developer Experience at Vercel, explains new concepts and foundations of Next.js app router, including layouts, dynamic routes, and data fetching. Deploy today: vercel.fyi/app-router
⌛️ Timestamps:
0:00 Introduction
0:10 Routing
2:57 Dynamic route segments
4:53 Data fetching
7:36 Caching
11:42 Metadata
💻 Resources:
◆ Routing: nextjs.org/docs/app/building-...
◆ Caching: nextjs.org/docs/app/building-...
◆ Metadata: nextjs.org/docs/app/building-...
#vercel #nextjs 
Наука
Bro just explained half of my Next JS problems in 15 mins! Wow! This guy is good! 👍👍👍
beacuse it is by next js original channel
This was an excellent demo. Concise, brief and to the point. Thanks Lee!
Thank you, this made my day 😁
This guide really answered almost all of my questions, it's short and straightforward. You're doing a great job.
Same thing I said. Like it was really packed with information and yet short.
I didn't know you have a RUclips channel. I was trying for hours, reading the documentation and failed. And here you explain everything in just 15 minutes. Thank you for the video!
Love NextJS!!! Y’all are doing amazing innovative changes and I can’t wait for the app folder to be in production!! I’m hopping it’s coming in the near future. Keep up the great work team!!
Literally, the only thing new was the last stuff with Metadata
nothhing innovate ... it has been part of nuxt.js since for ever ...
Its now stable!! Horray just as i got back to next js
Ai generated comment
@@tabletuser123 nope I’m real lol. Your account name looks AI generated
Is there a difference between no-cache, no-store and next.revalidate: 0?
This guy should keep posting videos, the examples and the way he explain things are just amazing
thank you so much for this video, i am new to nextjs and i know noone that knows nextjs 13, so they couldnt help me with a problem i got with routing. but then you came!
Love these new improvements. This is why I love Next JS ❤
used nextjs in my senior capstone project, it's blowing everyone away!
Thank you so much vercel and @leerob , very short and informative video , i really like the app directory .
Light years ago music was on vinyl records, then on CDs and now it's streamed from cloud.
Movies were on VHS, later DVDs and BlueRays - now it's streamed from cloud.
Video games... can't ever remember all those consoles but now it's all digital and also you can stream playing in cloud.
Finally webApps - your UI had been rendering on your device's broweser for days or rendered server-side...
...until now.
It's time for streaming era even in webdev with UI Streaming!
Simply render component, cache or revalidate it and serve to clients! Just this tiny piece!
FINALLY
I am sooooo hyped for the stable release you can't image. Love what u doing guys
Currently using this in my next project and it’s so much easier to route between pages
Love it make me want to use nextjs every single day. You’re an amazing team with an amazing product. Huge kudos for all of you and a special thank to you Lee for your videos
Appreciate the kind words :)
i admit, this is truly fantastic! thanks to you amazing people of vercel and to you Lee, you're awesome.
i'd love to know more to understand fully...
Dude you legit saved me. Was spending so much time on this. This is the only video that helped me
Very helpful!! Hope to see more videos like this!!
very straightforward, love it
Thanks! Those new features are really neat.
I love Next.Js. Keep on going guys.
Thank you!
Thank you! I'm not an expert in NextJS and in their docs for app router, couldn't find any mention of utilizing params to get the id from a dynamic route. I was messing with headers, pathname etc when params would have been fine. You helped me so much. Now I'm just trying to figure out why pages in my dynamic routes don't use the root layout (the page itself takes over the whole screen and the root layout is gone)
Super excited to use this in prod soon!😁
Extremely helpful video, thank you!
Clear and to the point: thanks!
I have been using app router for a few months on few of my production projects, and very impressed with the results. I'd love to see videos on how to implement GTM/GA, and posting data e.g. updating user details in a form.
Great suggestions!
Yeah this would be great, seems work on mutations is still ongoing for now…. But it seems the app directory is reaching stable, started a new SAAS project with it and hopefully it doesn’t end in tears 😂
Excellent delivery!
This is a great refresher and summary of all the awesome features of the nextjs app directory. I'm curious if there are any implications of setting the cache: no-store parameter on the fetch keyword.
Thank you for the info on how to route one page to another without a link tag.
Just what I needed, awesome!
This is the future of Web Developement!!!!
Yes. This is very helpful. Thank you.
very well explained! just wow
this is BEAUTIFUL!!!!!
Amazing stuff ❤
Brilliant innovations!
Thank you team vercel for explaining the concepts!
Thank *you*!
@@leerob you're welcome
Once the remaining router bugs are fixed, this will be amazing
Next finally cracking Jekyll's layout feature 13 years later. But good demo of the data fetching behavior from Lee!
Amazing great work!
In 13:35 it's mentioned that "these are automatically deduplicated". If in getRepo was passed fetch({ cache: no-store }) would generateMetadata and Page make only one or two requests each refresh?
Full stack industry level application tutorial needed for all the best practices and application
Love the app directory, made my life so much easier!
Glad to hear it!
@@leerob Hey Lee, can you please share with us the VSCode theme that you were using during this video?
Great thanks..finaly i got it
Thanks for this amazing video
I can't wait to use the app directory stable
Finally i get the solution of routing. Huh. Please mention this specifically clear in the your website.
You just have save my project before I turn crazy, tx comrade
Leerob is fcking amazing!!! I love these videos!!!
Wow, never been so happy to be told I have to re-write my code base ... what's NEXT ;)
1) As has been asked below, how do we now define a list of paths for prerendering - previously done using getStaticPaths Method? The docs do not seem to detail this specifically?
2) Observation - the generic naming convention for Page and API routes will make searching for files during development a bit of a task?
Thanks a million - super framework.
I'm learning NextJS at the moment and I have the same question about the generic naming convention. I opted for the old routing system because I want each file to have a more descriptive name.
I'm still trying to understand the advantages of the new routing system, so if anybody can explain, please do it! thank you :)
İt s been incredible helpfull. Thanks
Thank you for this video. It is so informative.
I have one question for Lee, how does he get his cursor to move so smoothly?
clear explanation
Excellent to the point(s) video.
Is there a code repo with the examples, so I can save time remixing and experimenting?
Thanks Lee
This is awesome. If my main data source is prisma, is there a way to leverage this caching mechanism, without losing the type safety provided by it?
Please make a video on, Deployment. How to optimize and the proper way to deploy your app for the wild in new nextjs 13 way
Hi, thanks for tutorial! What icon theme are you using here? :)
Keep going sir.
very helpful
Awesome!!!
Just have a question about generateMetaData :
We need to do a getRepo twice (inside component and generateMetaData)
I think it's a shame that we can't make this call only once to reuse the response of the getRepo in component for the generateMetaData...
Isn't there another way to make a single network call?
Thanks!
Bingo! at least would take data from the Page params
Had an issue where halfway through development we needed a page that we did not want to use the root layout. Seems like the only way to do that is to split that one page and the rest of the site into two separate folders in the app directory, each with their own layout. Tried doing that but as a result all my imports / paths broke.
Is there an easier way to go about creating different root layouts? Or opting out of a root layout?
I have been thinking the same, on how to out out of a certain layout for a specific page that is deeply nested. Like I would like to have root: layout work and layout level 2 work but I don't want layout level 1 to be included in the same route. Like how do I avoid that. Right Now The only way of doing it seems to be, not using layouts and instead use it as components that you can import like how we did it in the old nextjs.
Nice video! Could I know why every time when you type new lines of code, the "code hints" in grey colors already know what you are going to type? Any plugins abt this? Thx
What If I have some dynamic data on one route and I navigate to another route where I add to that data with a post request (for example a blog post) and If I navigate back to the previous route (without refresh) I want to see the fresh data list (post list) with the new item added? What can I use it to invalidate the cache and make Next.js to call the fetch again without refresh?
Is there a way to support static generation for dynamic routes similar to exporting fallback from getStaticPaths before next 13?
Could you please tell us the extensions that you are using to speed the development ?
Great 👍.
Great content! I just wanted to ask, since fetch is the API that was extended to support some of this caching stuff, I'm guessing using something like axios it just won't support all of these features? Is there a way to make it work even with something like axios?
I don't think so. If I'm not mistaken, you can use the new react cache function. That's the way to do it with database queries as well, I think.
export const revalidate = 60 //one minute
@@abdulramonlasisi3385 I'll have to try that out, but thanks. I was under the impression all of this requires fetch API to be used.
Thanks a lot
Do I see an API folder in the app directory! Would’ve love to hear about that.
Great video
When the app folder will be stable do you know the date ?
What caught my attention was proposing type properties in Repository type definition. How VS Code have done that?
The cache control, only works using the native fetch api ? or can I have the same behavior using axios for example?
I'd love to see a state management video for Next13. How server data can be hydrated on client to add interaction
just pass props to a client component, that simple :)
@@zuma206 large apps don't use prop drilling. They have their own client store
@@RedVelocityTV I think you would just pass the props to the layout where it can hydrate the client store, just like with the current pages system
usually, you don't need to think about state management in an old-fashioned way, now all requests are cached by default so you just need to create the function `fetchSomeShit` and reuse it. For a client-based state, you can use old approaches as well
THANK YOU
The big thing here is being able to import npm packages like embedded tweets, unsplash images, etc, that do their own fetching on the server. The bad side is that the nesting is incredibly quirky, and waterfall-prone. If there's not enough education on the subject, the level of apps will reduce, and the number of new apps passing the performance criteria will reduce dramatically. The architecture allows for bad fetching. But well so does react-query, apollo client and friends.
Like you said...it really blows my mind 😅 #Amazing
Is it good to fetch data in both functions
Page and genratemetadata
How to reuse the same data when i am using axios
Which extension is used to predict all the async await fetch code generation that we see in the video?
Thanks for sharing! I am confusing what different between images in source code and in public folder (performance, bundle size, ... ) and what is the best practice?
Can you use anything other than [id] for your dynamic route folder? I tried using something else but it doesn't work. Maybe I'm doing it wrong but I'm not getting any errors
thank you
For everyone wondering what icon pack it is, it's vscode-icons
Video about auth with new Next would be nice. How to protect routes and such
I prefer nuxt. But yes this is the way. Strapi is one of my favs. Headless WP isnt anything to scoff at though.
There are frameworks that exist solely for headless WP and with its extensions of plugins.
When experimenting with dynamic routes and looking at the x-vercel-cache header I noticed I only got a HIT on static routes, as soon as I used a dynamic route, like the blog post in the video, it resulted in a MISS. Why can I get the same level of caching on dynamic routes? Caching should be more dependent on the data on the page than the actual url.
What extension are you using to get that "searchParams" autocomplete?
Can I load data in layout.tsx and pass some of the data as a props to page.tsx which is layout children?
How would the app know how many ISR pages it has to store it statically first at build time?
Please also talk about how to share data between all these components with data being cashed on server, How to add styles. If there are any gotcha as it stands right now.
is there a way to combine between getting the data from a server component and the use of "use hook" on the client component to avoid passing props??
Can i just ask how do i generateStaticParams using prisma. Because for some reason i always get undefined instead of receiving array of ids and generates a type error when i try next/build
I love this but I really miss a way to update the data when the user has interacted with an element, like updating their profile using a button.
When using useSWR you can execute mutate(), and then the data is updating. Do we have something similar?
Thanks
So cool
I have but one question which i am currently having an issue with and that is if the data is being cached and then we go to dynamic route such as blog/1 we can access the id through params but is there some way to use the data that exists inside the cache already to also be sent to that so i can access that data inside my dynamic routes or do i have to refetch the data again inside that dynamic route?
but how do i change the title of my page based on dynamic, client-side state? say, a text input for example?
Whats the best way to handle Auth and Pass state from server to client
As you mentioned that the app router is almost towards full stability, would you recommend using the app router if I am starting a completely new project?
Anybody? Thoughts?
Thanks Nextjs team, you're making the world of dev a better place and without headache.
How do you manage localstorage in next. As we can't access it since next prerenders on server, right?
use LocalStorage in a client component 'use client'@@depression_plusplus6120
This is cool but how can we use middleware inside the app dir folder? Is this already developed? I am using one on the root but I need more for my app. Thank you.
Middleware is supported!