WebComponentFactory
lit-style
| WebComponentFactory | lit-style | |
|---|---|---|
| 1 | 1 | |
| 0 | 9 | |
| - | - | |
| 4.2 | 10.0 | |
| 6 months ago | over 1 year ago | |
| JavaScript | JavaScript | |
| - | GNU Lesser General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
WebComponentFactory
-
Web Components Eliminate JavaScript Framework Lock-In
Rather than putting the HTML in JS, you can fetch HTML in the JS.
E.g. https://github.com/g-utils/WebComponentFactory
lit-style
-
Web Components Eliminate JavaScript Framework Lock-In
I will read those links you referenced later. But what I think about the Shadow DOM is that that is for me actually the killer feature. That prevents a lot of weird issues. But it also brings limitations to methods of how web developers are used to do things, like applying styles globally, or having some sort of dependency between deeply nested elements, crossing the Shadow DOM when using Web Components.
What people usually try to do is to somehow open up the Shadow DOM for certain things, to make some things allowed to pass, or global. But I think might be a bit holding on to an old familiar habit. And I think there are better ways of structuring a project with Web Component in mind.
For example, you can create a base class from which all your components extend, and put the base style in that base class, and have your components add style on top of that. I implemented this method in a tiny library which makes it easy to use [0].
But yeah it is hard for most developers to adopt a new way of thinking. And as long as the new way doesn't provide that much improvement over the old way, it won't get adopted. But I think the idea of Web Components still needs to be integrated more in the web dev community. And maybe they will manage to make some changes to make the adoption easier.
And besides that, of course Web Components still have lots of other issues. But for me it has reached a point where I don't feel the need for React anymore. I rather live with some quirks in Lit than doing things with React, which just feels clumsy to me now.
[0]: https://github.com/gitaarik/lit-style
What are some alternatives?
lit-state - Simple shared component state management for LitElement.
nano - 🎯 SSR first, lightweight 1kB JSX library.
butterfloat - The greatest view engine for the modern web
React - The library for web and native user interfaces.
lit - Lit is a simple library for building fast, lightweight web components.