[dabbott]

Thanks for the feedback! This is super valuable.

1. There isn't anything fundamental about that tool that requires React. We have a lot of React experience and it's a very popular framework, so it made sense for us as a place to start, but we can definitely consider supporting other options.

2. Absolutely! We have a first draft of our mapping protocol already that works reasonably well, but still needs more iteration before we open things up. It supports a custom hook for attaching things to the DOM, so shouldn't require React specifically either.

Can you share a little about how you use web components, so we can better understand what an integration should look like? Do you use any kind of JS framework (at build time or runtime)? Do you use JSX, or is it all vanilla HTML?

[claytongulick]

Pretty much vanilla, but it depends on the component.

For components that need reactivity and have frequent renders, I use lit-html for rendering on a property setter change.

I mix and match components from different frameworks, I use vaadin-router, but sometimes include lightweight components from other systems too (ionic, shoelace, mwc, etc...).

Mostly though, it's just light-dom vanilla Web components with bootstrap (or similar) for base styles.

[dabbott]

Got it! Thanks for the info, it's very useful to understand the workflow.