Symbol with Content Input causes hydration errors in Next.js

[oscar]

Hello Manish,

I’ve already gone back and forth between React SDKs, and the Gen 2 SDK for React performs poorly.

When I profiled my application with it, the main thread on the browser blocked for more than five seconds on the same task, whereas the Gen 1 SDK, which is built on actual React code and not extruded through Mitosis, splits the tasks and exploits concurrency effectively.

Additionally, I’m not sure why you’re recommending this, since the engineering team is clearly aware of such issues, and claim it’s not recommended for production:

Builder React V2 SDK

Hi, My name is Veronika and I am a Customer Engineer here at Builder. The V2 SDK for React is currently not being recommended for production just yet as we’re working through some of the performance roadblocks. Some of the common concerns when switching to the V2 SDK would include increased bundle size - early versions of the SDK could include additional dependencies or less optimized code, resulting in a larger JS payload that could affect your page latency/ load time. There might be renderi…

Going back to the topic - we agree this seems to be an issue on the SDK side of things, as @c-eustaquio and I are using two different React meta-frameworks, but the same SDK generation.

I’m using the latest available version of the SDK, 7.0.1. Anything else that might be helpful for the team to investigate, feel free let me know.