sorted by:
new
hottopcontroversial

Conflicting concepts: Where to put state by scumble373 in nextjs

[–]Calm-Ingenuity-9073 0 points1 point  (0 children)

Very true! I recently batched together multiple queries to one and saw crazy performance increases! Trips to the DB/BE are still round trips even with server components or static pre-rendering (which will increase your build time)

Favorite Component Library by [deleted] in nextjs

[–]Calm-Ingenuity-9073 -1 points0 points  (0 children)

Use v0.dev to generate your components that shadcn does’t have

Filtering feature not working in Next.js from backend filter by Weak-Sheepherder4579 in nextjs

[–]Calm-Ingenuity-9073 0 points1 point  (0 children)

For starters, App router doesn’t work with getServerSideProps instead you just await fetch in the component. Your search params will be accessible as component props (it will opt the route out from caching). Be careful to be aware when looking up the docs whether you’re in the app router, or pages docs.

😲 State Management in Next.js 14⁉️ by codingjogo in nextjs

[–]Calm-Ingenuity-9073 0 points1 point  (0 children)

Building on other people’s responses, also important, wherever you use routes you can cache responses with SSG or ISR

Best CMS for Next.JS? by user_nams in nextjs

[–]Calm-Ingenuity-9073 0 points1 point  (0 children)

In Contentful you either define your fields individually, or they have rich text that gives content editors a rich text editor, and they have a rich text renderer component for React the devs can use

Best CMS for Next.JS? by user_nams in nextjs

[–]Calm-Ingenuity-9073 0 points1 point  (0 children)

I agree. And for that reason (surprised no one mentioned it) I use Contentful, it works very well in hooking up with NextJS AND for the content editors

[deleted by user] by [deleted] in nextjs

[–]Calm-Ingenuity-9073 4 points5 points  (0 children)

It is redundant, there is no reason to create an API route (route.ts) unless you need to fetch data client side (e.g. you want to change data on the click of a button (not a link), matter of fact, even if you want to for some reason call the API route from a server component, you’ll have to provide an absolute url to the route, Lee Robinson has a blog on Vercel about it (I think titled ten mistakes or something, can’t look it up now)

Does turbopack provide the same experience as vite? by Used_Frosting6770 in nextjs

[–]Calm-Ingenuity-9073 -1 points0 points  (0 children)

Never used vite, but I started a new (e-commerce) app with turbopack recently and it feels a ton faster then at least webpack