Production site is using SSR even though I expect client-side rendering
Unanswered
English Angora posted this in #help-forum
English AngoraOP
So I have a site with a header containing some links to other pages (using nextjs' <Link> component). When I click on a link I expect the site to navigate to the page using client-side rendering, which it does in my dev environment via
So this is pretty confusing already, but hear this: On vercel if I go to deployments and I click on "visit url" for the current deployment it'll send me to the preview deployment yeah? uses all the same prod env variables and everything. But this preview deployment uses client-side rendering when routing to new pages.
I feel like I'm being gaslit rn (or just being dumb). Does anyone have any idea what's going on here? Why would my prod environment default to SSR when every other environment is using client-side rendering for routing?
For context I'm using
next dev. It also behaves as expected when I run next build && next start locally. But when I deploy it to Vercel, the production site uses SSR instead (i.e. when I click on a link, the site makes a network request to fetch a new page from the server causing a page reload).So this is pretty confusing already, but hear this: On vercel if I go to deployments and I click on "visit url" for the current deployment it'll send me to the preview deployment yeah? uses all the same prod env variables and everything. But this preview deployment uses client-side rendering when routing to new pages.
I feel like I'm being gaslit rn (or just being dumb). Does anyone have any idea what's going on here? Why would my prod environment default to SSR when every other environment is using client-side rendering for routing?
For context I'm using
next version 14.0.3 and am on the hobby plan on vercel1 Reply
English AngoraOP
Bump ðŸ«