It’s sounds interesting! Can you describe a use case for this feature, please?

I haven't had much time to think about all the use cases for it yet, it's an idea that just popped into my head, but the initial idea is that this would allow for the development of <TextInput> components, either in react-figma, or an external package. As there is access to runtime events with react-reconciler, there's a lot of possibilities for new workflows and apps that can be built inside of Figma.

This could be a nice escape hatch too for avoiding use of the Figma UI API (e.g. for performance to avoid the use of a WebSocket bridge).

It could be really interesting to have "temporary" parts of a design such as checkboxes, buttons, text inputs that are rendered by a react-figma plugin/runtime, and can be removed when the plugin is closed, to allow for adding an API route for data (e.g. putting in GitHub usernames to get profile data from the API, etc). While this could be done with the Figma UI API with a socket bridge, I think having it as part of the same DOM as the Figma document would be amazing.

One idea, is that in code, you could have a system to help people populate mock-data into the document, where when you manually change the text to 2010-10-10 in the Figma UI, it auto-formats it with moment for you, like this pseudo-code:

const TextPlaceholder = () => {
  const [date, setDate] = useState('Enter date here');
  return (
    <Text onChangeText={(text) => setDate(moment(text).format())>
      {date}
    </Text>
  );
}