You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know that we can get static markup using getStaticMarkup or use renderToString, but how do I get js for interactivity? I don't know how to use plugins if this is the way. Is there a way that exists?
One thing that comes to my mind is using another react server to build the whole thing, but that too requires the config to .
What's the ideal way of doing this?
The text was updated successfully, but these errors were encountered:
@Roshan54321 What's exactly your use case? When you say JS for interactivity, are you talking about hydrating back to React? Why do you want to store HTML and JavaScript separately?
@Roshan54321 What's exactly your use case? When you say JS for interactivity, are you talking about hydrating back to React? Why do you want to store HTML and JavaScript separately?
But it's hard to know for sure without knowing more about your architecture.
yes,but I have a large codebase where this builder is one of the features. I want to deploy a site irrespective of my whole codebase built from puck but how do I do it?
I can set aside the static html but I want interactivity too. Hydrating, yes, but how do I separate my whole codebase from just the site? That would compel me to make another React, but that too needs the config for Render.
I dont know if that makes any sense😅, but I cant find a reasonable way.
In a large application, the cleanest way is to split the rendered Puck output into a separate application. A a monorepo can help to easily share components.
Alternatively, you can trust in code splitting rather than worrying about splitting up the HTML and JS.
I know that we can get static markup using getStaticMarkup or use renderToString, but how do I get js for interactivity? I don't know how to use plugins if this is the way. Is there a way that exists?
One thing that comes to my mind is using another react server to build the whole thing, but that too requires the config to .
What's the ideal way of doing this?
The text was updated successfully, but these errors were encountered: