Now you CAN so it so that is not the case, but tbh i have never seen that in the wild -
Now you CAN so it so that is not the case, but tbh i have never seen that in the wild -
How does the rest of your codebase look?
This is the primary problem with web components. No frameworks sounds nice in theory, but it only solves about 30% of the problem. The rest ends up an ad-hoc mixture of libraries and custom code for state management, routing, styling, cross-component communication, etc, to the point that you end up building your own framework that is brittle and unmaintainable. Applications like this generally end up as a huge confusing web of global event buses or with multiple tightly coupled layers of prop drilling because of that.
There was a dream that was web components once upon a time. It felt like the future. But the APIs ended up half implemented (poorly), and the spec was more or less abandoned by everyone but Google. Browser vendors could have done things right, and focused on pulling in the good things from the framework world (i.e. what happened with jQuery), but they didn't.
edit: the types on remeda look great though! If I were doing a backend-only NodeJS project, I'd be super tempted to test it out.
it's because they hired "frontend" developers to develop these features, likely someone with little actual compsci experience, and have little to no room to make the feature and under a tight deadline.
My only success has been internal reviews of wcag compliance and the threat of fines if found lacking.
But for non digital design its embarrassingly hard