While the library is pretty stable and has not seen major overhauls in the last while, it could always be improved. We welcome both suggestions and contributions from the community.

Here are some partial list of future directions that this library could explore:

- `@angular-vue` - Just like it sounds like. `@angular-react` was created with React in mind, but is not limited to it, and most of the concepts translate well over to other VDOM-based libraries, like [Vue](https://vuejs.org/).

  As described in the [render flow](./Architecture:-Render-flow.md#ReactNode), most of the abstraction logic is not specific to React.

  We can easily see someone needing the same thing as `@angular-react` for embedding Vue within Angular, and could leverage most of the code in `@angular-react/core` for Vue as well. While it would certainly be a separate library, we're open to the idea of creating a shared, library-agnostic core (on the side that is not Angular).<br>
  This is not unlike the separation and sharing done with [`dom-testing-library`](https://github.com/kentcdodds/dom-testing-library) and [`react-testing-library`](https://github.com/kentcdodds/react-testing-library), which the former is the base for [`vue-testing-library`](https://github.com/dfcook/vue-testing-library) and [more](https://github.com/kentcdodds/dom-testing-library#implementations).