Choosing Web Components does not mean opting out of frameworks like React. It’s like saying you can’t use a framework due to the presence of a certain HTML element
Comments
Log in with your Bluesky account to leave a comment
I think you should at least evaluate how you use the framework. Adopting web components should open opportunities to standardise around web standards. Examples: CSS, events, shared data contexts.
Exactly. Web Components and frameworks like React aren’t mutually exclusive they can work together. It’s not about choosing sides, it’s about using the right tools for the right layers.
I haven't used web components much, but aren't most built using some framework in the first place? For instance Vue has real good support for generating web components from what I've heard.
Web Components are just [HTML], [CSS] & [JavaScript]
So you can build Web Components with any *tool* that outputs these standard technologies.
Or use Notepad if that makes you happy.
There is a difference, if you use Framework tools you are always framed by the Framework VERSION
Oh, I meant "view library", not "framework". Lightweight libraries like Solid and Svelte seems like a good fit here so you get some abstraction over the DOM, though as I said, I haven't tried this myself.
Pretty much what Danny said! I don’t think it’s a bad idea to use frameworks to help you build out web components. You just need to be aware of the caveats such as bloat and compatibility
Comments
So you can build Web Components with any *tool* that outputs these standard technologies.
Or use Notepad if that makes you happy.
There is a difference, if you use Framework tools you are always framed by the Framework VERSION
Maybe not even a good fit.
Do try running a mix of versions on one page before you commit yourself to any Framework/Library
Only Vanilla JavaScript is backward compatible