Static badge but dynamic on compiled?
Answered
Whiteleg shrimp posted this in #help-forum
Whiteleg shrimpOP
Hi, I have a full client-side route "/tenant/[tenantId]", but I don't use the parameters coming from the parameter hook, but from useParams. In development mode, the static badge appears in the bottom left corner, but when the next build is run, it is marked as a dynamic route.
It works perfectly, no issues. I'm just curious if this is an intentional behavior or just a bug.
It works perfectly, no issues. I'm just curious if this is an intentional behavior or just a bug.
Answered by B33fb0n3
that sounds more like a bug between the build log and the log on the page itself
5 Replies
@Whiteleg shrimp Hi, I have a full client-side route "/tenant/[tenantId]", but I don't use the parameters coming from the parameter hook, but from useParams. In development mode, the static badge appears in the bottom left corner, but when the next build is run, it is marked as a dynamic route.
It works perfectly, no issues. I'm just curious if this is an intentional behavior or just a bug.
that sounds more like a bug between the build log and the log on the page itself
Answer
Whiteleg shrimpOP
in this case, which is the expected behavior? to be static or to be dynamic?
@Whiteleg shrimp in this case, which is the expected behavior? to be static or to be dynamic?
Your page will be dynamically served (what the build log says)
Japanese littleneck
I upgraded my app to Nextjs 15 and I saw the indicator that says static route, even though it's a dynamic route, I was curious about it if it's a bug in v15 or there is some weird behavior going on.
Anyway I'm glade I found your post and found out it's a bug, otherwise I won't be able to sleep tonight thinking about it 😅
Anyway I'm glade I found your post and found out it's a bug, otherwise I won't be able to sleep tonight thinking about it 😅