Re:Does anyone "love" Next.js's new App Router?
by jo_beef on Sunday December 31, 2023 @11:32PM
(#38829748)
I'm currently building a project using App Router. Here are my thoughts so far:
1. In React Server Components, you fetch data at the component level instead of route level. You can pass the data down as props if it's a client component.
2. I'm not sure if HMR is faster in Pages, but in App Router it tends to be slow. I always use --turbo to see changes quickly, but it can still be a bit buggy.
3. I just found out that using "use client" directive isn't actually sending 100% javascript to the client. It's just a replacement of serverSideProps. The component is rendered both on the server and the client, which can be confusing at first. You can disable SSR using dynamic imports.
4. I actually like Route Groups, best feature by far.
1. In React Server Components, you fetch data at the component level instead of route level. You can pass the data down as props if it's a client component.
2. I'm not sure if HMR is faster in Pages, but in App Router it tends to be slow. I always use --turbo to see changes quickly, but it can still be a bit buggy.
3. I just found out that using "use client" directive isn't actually sending 100% javascript to the client. It's just a replacement of serverSideProps. The component is rendered both on the server and the client, which can be confusing at first. You can disable SSR using dynamic imports.
4. I actually like Route Groups, best feature by far.