3 ms·
It is increasingly important that we publish components in a framework/library agnostic manner. Not only do we have a lot of duplication of component libraries
by brylie 7y ago
It is increasingly important that we publish components in a framework/library agnostic manner. Not only do we have a lot of duplication of component libraries in general, but we also hit the landmines of "Angular-oriented", "Vue-oriented", "React-oriented"... Hopefully, we will ser more full fkedged component libraries built with Web Components, which can integrate with any framework or library.
- capableweb 7y agoYou don't have to wait for web components though. If the authors of said libraries split it up in two parts, the main logic and framework/library integration, the sharing would be possible today already. I think tools like xState gets this right, you can glance the package listing here: https://github.com/davidkpiano/xstate/tree/master/packages https://github.com/davidkpiano/xstate/tree/master/packages Then you just include core + framework X integration, and if you need a new integration, you create it new and use it together with core.