4 ms·
I didn't like that the components are all web components with their own shadow Dom inside. Makes styling really hard and didn't work with tailwind for example.
by andix 3y ago
I didn't like that the components are all web components with their own shadow Dom inside. Makes styling really hard and didn't work with tailwind for example.
- Bytewave81 3y agoNot just that, but it basically makes the library incompatible with serverside rendering a la Next.js. We actually explored using Shoelace for a project but ended up having to choose something else instead because of this.
- neeleshs 3y agoWhat did you end up using?
- Bytewave81 3y agoWe settled on Chakra (https://chakra-ui.com/ https://chakra-ui.com/). Although we also abandoned our ambitions of a Next.js migration, so... I guess it didn't really end up mattering all that much anyway.
- neeleshs 3y agoThank you
- andix 3y agoTrue, it completely relies on client side rendering, and it's impossible to render it server side. With disabled Javascript it doesn't show anything at all. I would really like to use it, but using it feels like limiting your options much more than necessary. Even the CSS-in-JS based libraries (like React MUI) allow SSR to some extent.
- mondrian 3y agoI guess the advantage is that you can drop them into any HTML page and they look and work correctly. And you can control them with plain JS, like `document.getElementByID(dialogId).open = false;`
- andix 3y agoProbably, from my perspective (using a frontend framework) this doesn't sound too helpful though.