Post

@justinfagnani.com I’ve been using Lit’s base ReactiveElement, without a “render” method, since we’re inserting the shadow template externally, and updating it imperatively. Curious if you think this makes ReactiveElement overkill? We use it for the “update” methods and syncing props & attrs.

19/5/25, 1:52 am0 reposts1 like

Justin Fagnani

@justinfagnani.com

19 May 2025

Doesn't sound like overkill to me. ReactiveElement takes care of a lot of property/attribute bookkeeping that might be annoying otherwise. It also handles CSS for you, but you might not be able to use that.

Rogin Farrer

@rogin.dev

19 May 2025

Also not using Lit styles. (We're maintaining our own server integrations for injecting DSD and styles.) Is the async batching part of the prop/attr bookkeeping? What Lit does for that is great, but I'm thinking about whether a different implementation without asynchronicity would be better for us

Rogin Farrer

@rogin.dev

19 May 2025

I’ve had to create our own version of “updateComplete” and “firstUpdated” since the shadow DOM or light DOM weren’t necessarily available/ready when we expected.