Martin
Explore posts from serversTTCTheo's Typesafe Cult
•Created by Martin on 10/17/2023 in #questions
NextJS Static Export
And then getData is:
18 replies
TTCTheo's Typesafe Cult
•Created by Martin on 10/17/2023 in #questions
NextJS Static Export
I added console.logs in my code (I am a pro in debugging..) and I saw it coming as the third. I'll accept I solved it by removing the cache disabling. Took me too much time to dive into this.
18 replies
TTCTheo's Typesafe Cult
•Created by Martin on 10/17/2023 in #questions
NextJS Static Export
But the generateStaticParams did generate just the normal expected parameters, 1 and 2.
18 replies
TTCTheo's Typesafe Cult
•Created by Martin on 10/17/2023 in #questions
NextJS Static Export
Well, in my logic (the default Page function) I saw two requests for the backend articles (1, and 2) as expected. Then I saw also a request going to /articles/%5Bid%5D which is url-encoded [id].
18 replies
TTCTheo's Typesafe Cult
•Created by Martin on 10/17/2023 in #questions
NextJS Static Export
Ah yes, I added a revalidate set to zero. Now to understand why that somehow then triggered to call to the route with the foldername itself
18 replies
TTCTheo's Typesafe Cult
•Created by Martin on 10/17/2023 in #questions
NextJS Static Export
I am now checking if I added a disable cache
18 replies
TTCTheo's Typesafe Cult
•Created by Martin on 10/17/2023 in #questions
NextJS Static Export
I do not understand the former part of your question. Something (I do not know what exactly) is doing a call to
:8080/articles/[id]
with [id]
url encoded. Should caching be disabled manually when you enable the output export
?18 replies
TTCTheo's Typesafe Cult
•Created by Martin on 10/17/2023 in #questions
NextJS Static Export
I don't realy understand yet where it comes from and why it is done. And the documentation of NextJS does not seem to help me any further as well
18 replies