I wanna ask a question which is so very important for most of us. Somehow plasmic have made it very painful for us developers to use different dynamic & csr code as components & use them within plasmic.
So I am using lowcoder to create apps fast & its a client side rendering system. I created a component using its SDK & registered it into plasmic.
As nextjs is a SSR it gave me window refrence errors so I used next/dynamic loading. Now the nextjs page doesn’t render or show it…
1st. I want to create & use components embedding dynamic & Custom Client Side Rendering apps/modules via their sdk’s & not iframe.
Then after registering those components in plasmic use those components as usual in plasmic but they don’t work. Also, If I place them in a seperate pages not created via plasmic, they work.
2nd. Create components which not only get registered in plasmic but also are compatible so they can be further edited via plasmic studio.
@illuminating_egret As you mentioned the lowcoder is a client-side rendering system. It might be using window object internally which would be causing the issue on the Nextjs SSR during hydration. I think the following will resolve it.
Add the window undefined check at the beginning of your code component, before returning the lowcoder component. It will supress the window reference error.