Feature Request: Native Web Components Implementation

[mhoad]

I am not sure if this is the right place for this or if this is something you would even consider to be as within the scope of the project but I wanted to propose that while we have an Angular implementation of the components that it might also be beneficial to develop a native Web Components implementation that was framework agnostic.

The main benefits as I see it would be:

1. Native Web Components would allow each component to be integrated with any of the main front end frameworks not just Angular thus improving the potential reach and impact of the project.
2. It also allows the use of the components without any kind of framework and could just be used with nothing more than native browser APIs.
3. All the obvious future proofing of the project that would come as a result of points 1 and 2 above.

[nnixaa]

Hi @mhoad, this totally sounds beneficial. Moreover, since Eva and implementations are Open Source - we believe the community may also use this as an opportunity to contribute to the ecosystem.

Let's keep it open to see the interest.

[colshacol]

For anybody to actually use Eva for an app they will have to create some form of components (framework specific, web components, or css classes implementation) in order to bring it to life.

This work will be repeated by hundreds of teams.

And when I create Eva JS components for a work project that doesn’t allow open sourcing, I’ll have to rebuild that library completely when I want to use Eva components in a personal app!

This feature needs to be in progress ASAP! And I am more than willing to spearhead (or contribute quite a bit, at least) it, keeping it dependency free and light weight.