Vanilla or web component implementation of Visual Editing

[osnoser1]

Well, it generates noise when I see that react is added as a bundle in an angular app, and the bundle size really increases a lot. I started a custom implementation in Angular, but the downside is that if you make updates to the UI, I'd have to update it too, and that can generate friction on every UI or logic update.

Is there any plan to expose visual editing without using react? Maybe using a js or web component implementation to help reduce the bundle size of the package?

In the end, I'm not so sure about the value of an angular implementation, and it could help the sanity community explore the idea of a pure implementation.

Thanks for your fantastic work.

[stipsan]

Hi!

I agree that deps like react, styled-components and more are too heavy for what we need.
We've started adopting xstate for more complex state, as an alternative to react-only libraries like zustand.
However we're currently blocked by what @sanity/ui supports, which is also what's requiring us to use styled-components.
Until those blockers are taken care of I'd say it's high risk to attempt an angular version. As you say, it creates a burden on applying the same features and work on our react version, with the angular one.
In the mean time we recommend using lazy loading techniques to ensure the visual editing library isn't ending up in your production bundle.