Brian Rinaldi is a Developer Experience Engineer at LaunchDarkly with over 20 years experience as a developer for the web. Brian is active in the community running CFE.dev and Orlando Devs.
I don't know the specifics of your use cases obviously, but I find that it's often a matter of changing how you approach a specific technical requirement from a server-side dynamic solution to a client-side dynamic solution. What I mean by this is that rather than solving the problem with a new page request, we might be able to solve it with a client-side request to an API or serverless function (there is always a server involved somehow 😉) and then some JavaScript to change the client state/update the UI. That's all Next.js is doing with SSR after all and why it can be enabled on services like Netlify even though they are "static."
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don't know the specifics of your use cases obviously, but I find that it's often a matter of changing how you approach a specific technical requirement from a server-side dynamic solution to a client-side dynamic solution. What I mean by this is that rather than solving the problem with a new page request, we might be able to solve it with a client-side request to an API or serverless function (there is always a server involved somehow 😉) and then some JavaScript to change the client state/update the UI. That's all Next.js is doing with SSR after all and why it can be enabled on services like Netlify even though they are "static."