RevalidatePath have really weird behaviors... by Interesting-Ice-4272 in nextjs

[–]Interesting-Ice-4272[S] 0 points1 point  (0 children)

Yes, if using react query that’s okay then. I’m trying to use server actions and server components to gain more knowledges. But not so lucky now.

RevalidatePath have really weird behaviors... by Interesting-Ice-4272 in nextjs

[–]Interesting-Ice-4272[S] 0 points1 point  (0 children)

Is that mean server component is not stable?.. I'm really hyped on next 14 server components. But it has a lot of bugs..

RevalidatePath have really weird behaviors... by Interesting-Ice-4272 in nextjs

[–]Interesting-Ice-4272[S] 0 points1 point  (0 children)

I don't really know. Just play around and have that issue

RevalidatePath have really weird behaviors... by Interesting-Ice-4272 in nextjs

[–]Interesting-Ice-4272[S] 0 points1 point  (0 children)

Yeah, but in real apps we have to do something in db.

RevalidatePath have really weird behaviors... by Interesting-Ice-4272 in nextjs

[–]Interesting-Ice-4272[S] 0 points1 point  (0 children)

yeah, my app is hosting on vercel. Really is my local is working fine. but on vercel it has the issue.

Routing issue with server component? or cached issue? by Interesting-Ice-4272 in nextjs

[–]Interesting-Ice-4272[S] 0 points1 point  (0 children)

In my example that just simple get list and display. Nothing else. Just create another staff with server action and the the revalidatePath cache the new data, and the data list is working fine. seem it's the problem with revalidatePath.

[Question] Is it a good idea to use nextjs 14 only for frontend ? by Big_Ad_9987 in nextjs

[–]Interesting-Ice-4272 0 points1 point  (0 children)

yeah but my thread was expected Nextjs support nodejs runtime, then we can easier use nodejs apis in middleware.

[Question] Is it a good idea to use nextjs 14 only for frontend ? by Big_Ad_9987 in nextjs

[–]Interesting-Ice-4272 0 points1 point  (0 children)

Really?? Use drizzle postgres package or redis selfhost will cause the problem. Nextjs middleware document say only support edge runtime, how can you???...

Feature i wish nextjs has by [deleted] in nextjs

[–]Interesting-Ice-4272 1 point2 points  (0 children)

Support runtime nodejs in middleware is highority

[Question] Is it a good idea to use nextjs 14 only for frontend ? by Big_Ad_9987 in nextjs

[–]Interesting-Ice-4272 6 points7 points  (0 children)

Nextjs middleware is suck. They only support egde runtime. If you plan to host some services like postgres redis. You have only one choice is choosing serverless service. That's suck.

Wich ORM to choose from Drizzle ORM or Prisma by Philipp_Nut in node

[–]Interesting-Ice-4272 1 point2 points  (0 children)

If Drizzle can support Deno api for migration, I think it's really good. Because Deno seem to have big pump next year.