hellyeah
TTCTheo's Typesafe Cult
•Created by hellyeah on 7/18/2024 in #questions
Next.js caching
i wonder what all those setting do if they dont help
12 replies
TTCTheo's Typesafe Cult
•Created by hellyeah on 7/18/2024 in #questions
Next.js caching
tho it works for that particular simple case, it doesn't work with the case im facing in prod rn
https://github.com/HellYeahOmg/revalidate-test/tree/long-async-request
While sending a heavy request from the main page, users can navigate to other pages, and in that case even revalidatePath (or revalidateTags) doesnt help...
12 replies
TTCTheo's Typesafe Cult
•Created by hellyeah on 7/18/2024 in #questions
Next.js caching
updated the repo, main page has
export const dynamic = 'force-dynamic'
export const revalidate = 0
and the get request also has cache: 'no-store' policy
12 replies
TTCTheo's Typesafe Cult
•Created by hellyeah on 7/18/2024 in #questions
Next.js caching
@nyx (Rustular DevRel) i of course tried, but my mistake i didnt commit it
12 replies
TTCTheo's Typesafe Cult
•Created by hellyeah on 4/25/2024 in #questions
Next.js as a client API choice
@Pepperz which one?
Basically i see 2 ways of doing this:
1) ui uses a server action, which uses fetch and calls the real api, then triggers revalidatePath or whatever
2) ui directly uses fetch in a client component with manual refetching (be it fetch or router.reload)
both options seems to work i guess, just trying to grasp cons and pros
12 replies
TTCTheo's Typesafe Cult
•Created by hellyeah on 4/25/2024 in #questions
Next.js as a client API choice
Well, "client solution" means simply UI. So yes, i want to leverage all the server components stuff, but the api is already there, so some features just can't be used.
12 replies