Post

Slime
@slime.camp

can anyone tell me why it seems like the #webcomponents community doesn’t use Vite? i get they built their own thing before but at this point it seems silly to avoid it? Is there a good reason?

0 reposts0 likes

Joe Pea
@joe.trusktr.io

Why is it silly to avoid Vite? Probably not every app needs Vite. Vite is pluggable so technically any custom element framework that has specific build requirements can be plugged in, but that's only necessary when/if needed.

Slime
@slime.camp

because you end up reimplementing similar features in a bespoke way that you then need to configure and maintain. It’s just weird to go over to web components land and see a parallel universe of tooling that needs so much wiring when I’ve come to expect to be able to just add 1 plugin and be done

Elf M. Sternberg
@elfsternberg.bsky.social

I use Vite all the time. It's not exactly like you can avoid it since it's the driver under Storybook, for one thing. That said, I have a strong preference for The Unix Way (run tools that do one thing and do it well) and Vite is, well, one of those all-in-one shops where workarounds are painful.

Justin Fagnani
@justinfagnani.com

Never had the need. Web Dev Server and Web Test Runner work great. It also seems like Vite didn't handle CSS imports well. I keep hearing about people needing to use non-standard workarounds to load it.