3 ms·
While this is really nice, it's a shame that a VueJS developer is unable to re-use a React-based text-editor which already exists and he found it perfect. This
by mathnmusic 7y ago
While this is really nice, it's a shame that a VueJS developer is unable to re-use a React-based text-editor which already exists and he found it perfect. This is why Web Components start making a lot of sense.
- jeremyjh 7y agoIt is possible to use a react component in a Vue app but of course what it does to your page weight may not be acceptable. https://github.com/akxcv/vuera https://github.com/akxcv/vuera
- adrianhel 7y agoThis depends on the app however. For a landing page? No way. For a module within an app I would not mind, as long as lazy imports are used.
- woah 7y agoWill web components let him use a React module with Vue.js without loading both libraries and learning React? Or is web components a third library that is so much better that you don’t need the other two libraries? Is this the situation where there are too many standards and you can only solve the problem by creating another standard?
- mfatica 7y agoWeb Components should replace them both. They aren't standards - just frameworks developed by third parties. The Web Components standard is the official standard and should be the one people reach for
- mathnmusic 7y agoWeb components can't make React/Vue/Angular components reusable anywhere else, but web components themselves are reusable in React/Vue/Angular apps.
- philippkuehn 7y agoI didn't call it "perfect". Slate.js is great but has some downsides too. But for Vue.js there was like nothing, so I took the first step. There is also a core package of Slate, so it's up to you to build a wrapper for Vue too. Slate is still in beta. That's why I chose to built on top of ProseMirror.