Lit

“not having the limitations of shadow dom (Lit)”

“It's part of the OpenJS Foundation (formerly jQuery and Node.js Foundations)”

“Lit pretends are more complicated than they are because it also assumes you want to start from Shadow DOM by default”

“Much less boilerplate than raw custom elements.”

“You can inspect a Lit component directly in Chrome, it’s just a custom element.”

“now we're just using another framework with one small piece swapped out”

“super light web component libraries like Lit”

“Lit has been a nice middle ground for me.”

“Lit element is much more accessible if you want just web components, but with a sane syntax.”

“I'd reach for lit instead of adding the Sortable.js dependency”

“I have success with Web Components / Lit”

“I think their approach to state management using a context is limiting”

“Lit is great but unfortunately pretty much unmaintained”

“isn't maintained by it anymore. The project is, unfortunately, almost dead tho”

“solve at least 80% of the issues there were and are with just plain JS”

“the result is so much simpler”

“Lit's plain JS/TS, no-build-required approach is easy for LLMs to generate”

“Lit: each todo-item is an HTMLElement (C++ heap, ~124 bytes minimum)”

“Lit is not opinionated about your build system You can write Lit components in plain JS, going back to ES2015.”

“the framework is pretty opinionated on your build system in my experience”

“Lit is widely used to build very complex apps”

“There wasn't really much upside either. No real performance gain or superior feature, and you got fewer features and a smaller ecosystem.”

“Web Components API is verbose enough that you want to handle it with at least some abstraction.”

“Lit is "fully backwards incompatible [with] Polymer"? No, Lit and Polymer work just fine together because they both make web components.”

“It's a library that gives you better ergonomics.”

“the frameworks handle a bunch of stuff for you, like reactive properties”

“Despite being acrively promoted as "not a framework just a lib" it's rapidly sucking in all the features from "fast moving js"”

“Lit in particular is one giant memory leak.”

“a very lightweight and useful one”

“Lit is mature, but it's not more mature than React”

“the common WC base classes like Lit's ReactiveElement all do change detection on a per-property basis”

“My secondary concern with Lit is the additional complexity of using shadow and light DOM together”

“oh nice! I didn't know that you can just make it use light dom.”

“If you prefer global styles, you can render into light DOM instead with that one-line switch.”

“the hoops you have to jump through to style elements”

“while we didn't go with it, it was very nice”

“it's quite good, simpler to reason about than the current state of React imo.”

“We've finally removed the legacy Polymer dependency. All components are now 100% Lit-based”

“Lit has joined the OpenJS foundation to stay afloat”

“Lit is pretty good :-) Though it was never positioned as a framework. And it recently was liberated from google.”