Ah, this is important new information for me! I just visited the website, and looked for a virtual DOM API that I can use inside of my library. Unfortunately, when I read the actual "getting started", it showed me how to import react libraries for hooks, and use JSX, and so I concluded that:

(a) This is actually a React replacement, like Preact, not just a virtual dom.

(b) The homepage marketing is misleading! The project lost a bit of integrity for me at that point, and I started trusting it less.

If the homepage marketing is declaring it to be a virtual dom, then I want to see how to use the virtual dom API so that I can verify what it is! If it then on top of that has a React Compatibility layer, that's just awesome and makes me really excited to understand it, and I'll probably want to look at that layer so that I can see what React is beyond a virtual dom.

Anyway, do you have a pointer to how to use it as a plain old virtual dom? I happen to be in the market for one, right now!

To my mind React is a couple different things:

- A VDOM (a library that lets you construct a virtual-dom, and then reconciles it with the previous one, and patches the real DOM accordingly)

- A state management/reactivity system (state hooks, effects, etc, and really also class components and their state/lifecycle)

- A framework which ties the above two together into a cohesive package for building web UIs

For me, the term "VDOM" only refers to that first point; i.e. you could combine a VDOM library with some other stuff to make a React-like framework

That could just be me, though