Lit-style Alternatives

Similar projects and alternatives to lit-style

React

1,697 222,111 9.9 JavaScript lit-style VS React

The library for web and native user interfaces.
lit

141 17,575 9.4 TypeScript lit-style VS lit

Lit is a simple library for building fast, lightweight web components.
SurveyJS

surveyjs.io featured

Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
joystick

50 197 9.9 JavaScript lit-style VS joystick

A full-stack JavaScript framework for building stable, easy-to-maintain apps and websites.
webcomponents

34 4,313 4.4 HTML lit-style VS webcomponents

Web Components specifications
nano

5 1,416 5.6 TypeScript lit-style VS nano

🎯 SSR first, lightweight 1kB JSX library. (by nanojsx)
butterfloat

4 6 9.2 TypeScript lit-style VS butterfloat

The greatest view engine for the modern web
lit-state

3 137 0.0 JavaScript lit-style VS lit-state

Simple shared component state management for LitElement.
InfluxDB

www.influxdata.com featured

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
WebComponentFactory

1 0 4.2 JavaScript lit-style VS WebComponentFactory

Make use of JavaScript web components while keeping your code in .html for LSP features

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better lit-style alternative or higher similarity.

Suggest an alternative to lit-style

lit-style reviews and mentions

Posts with mentions or reviews of lit-style. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-11-27.

Web Components Eliminate JavaScript Framework Lock-In
10 projects | news.ycombinator.com | 27 Nov 2023

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