Vue Has Too Many UI Frameworks

williamhoyle.ca

2 points·willhoyle··4 comments

AFAIK Quasar is the only Vue UI framework that:

- Has documentation that doesn't have ads/sponsorships taking a good chunk of my screen (looking at you Vuetify)

- Has Vue3 support ready _today_ (although its Vue3 is still in beta) and is actively under development. Other frameworks say it's on their roadmap and won't be ready for awhile

My only grip with Quasar is that its Typescript/SSR support is quite lacking

Agree. I use Quasar at work for SPA and Buefy for personal projects which was one of the ideas for this post.

I thought SSR support was pretty good in Quasar? https://quasar.dev/quasar-cli/developing-ssr/ssr-frequently-...

The problem with Quasar's SSR is that you'll be locked into their CLI tool due to how much undocumented global state changes they do.

If you just want use it as a UI component library in an existing Vue SSR app, you'd have to at the very least:

- Call Quasar.ssrUpdate before instantiating the root Vue app. The devs also stated they have no intention of releasing the type definition for this _essential_ function [1]

- Extract app.$q.ssrContext.Q_BODY_CLASSES and add it to your <body> tag during your render step or else most of the css states will not work

These are the two main culprits I've found. Sadly my SSR apps still feel slightly off compared to a SPA with missing animations here and there.

[1] https://github.com/quasarframework/quasar/issues/8112#issuec...

It is death when you are building something complex that has parts snapped together from various sources so you not only need to choose one of four different <Button> implementations used in different parts of the app but you need to know the API details for each one, how to style it, etc.

Reply on news.ycombinator.com