Hmmm... I always thought Declarative Shadow DOM was pretty straight forward. I just don't think it scales very well for repeated components. - ThreadSky

About ThreadSky

stuffbreaker.bsky.social • 6 days ago

Hmmm... I always thought Declarative Shadow DOM was pretty straight forward. I just don't think it scales very well for repeated components.

Reposted from ændra.

I am not paid anywhere near enough to be messing with Declarative Shadow DOM at this stage of its development.

Comments

aendra.com•6 days ago

My use-case is I'm rendering the base HTML using DSD and dehydrated React, then trying to rehydrate the DSD as a React app in the Shadow DOM.

It is not going well.

stuffbreaker.bsky.social•6 days ago

Yeah, I can see a couple of road-blocks with that. What's the objective?

aendra.com•6 days ago

I'm working on a web component that dynamically imports a React app via ESM and renders it into the Shadow DOM. The goal is to encapsulate the app in Shadow DOM because the intention is to let privileged CMS users inject e.g. data visualisations into a page. DSD would help prevent CLS for that.

stuffbreaker.bsky.social•6 days ago

Are you SSRing the app within the component?

aendra.com•6 days ago

No, the SSR is intended to be done by a Lambda that generates the dehydrated DSD, which then gets rendered by the webserver.

techytacos.dev•5 days ago

If you run into trouble and if you're not already on it, the Lit Discord is pretty helpful for general web-component-related stuff and is probably the biggest concentration of people that have used DSD

https://lit.dev/discord

aendra.com•5 days ago

Oh that's really good to know — thank you!

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply