Hacker News Reader

Comment by wokwokwok | Hacker News Reader

I'm pretty surprised.

I recently did the same, and hand's down, the vue ecosystem is weak.

Vue is difficult to work with (unable to render content without a functional component wrapper, poor support for style libraries like tailwind), and the state management ecosystem is fractured between vuex and pinia. Worse, much of the help online is for old versions (vue2). Storybook 'out of the box' is broken and doesn't work at all (unable to resolve '@/...' imports).

It's been painful.

> Everything is intuitive and I am not googling days to fix tooling issues

That has not been my experience; I spent literally 3 days customizing my storybook install to make it work, and digging through 'try this...' threads on https://github.com/storybookjs/storybook/issues/11989

View on HN

> poor support for style libraries like tailwind

Can't relate. Tailwind works fine with anything that supports PostCSS. I run it with Vite and there's zero issues.

> the state management ecosystem is fractured between vuex and pinia

This is also just not true. Pinia is officially replacing Vuex as the recommended store library for Vue [1]. They're also vastly similar in how they do things, so the knowledge transfer over from Vuex to Pinia. And Pinia just address most of the design goals mentioned in the article in the most simple way.

As for Vue 2 -> 3 transition, lots of the larger UI frameworks in the ecosystem is struggling to migrate, despite lots of efforts on the compat layer to smooth the transition, which is a bummer. But as long as you're not doing those sophisticated things, Vue 2 examples should work out-of-box on Vue 3 as well. There are surely less resources for the composition API, but the official introduction guide has been good enough in my experience.

[1]: https://vuex.vuejs.org/#what-is-vuex

> As for Vue 2 -> 3 transition, lots of the larger UI frameworks in the ecosystem is struggling to migrate, despite lots of efforts on the compat layer to smooth the transition, which is a bummer.

I actually recently looked into most of the frameworks out there and their migration efforts.

So far, I only found three viable options for Vue 3:

  - PrimeVue https://www.primefaces.org/primevue/
  - Quasar https://quasar.dev/
  - Element Plus https://element-plus.org/en-US/

We went with PrimeVue and while using PrimeFaces was an incredible pain with Java, the Vue version seems a bit better. Then again, it's kind of odd that libraries as popular as Bootstrap don't have complete bindings in the form of Vue 3 components.

For state MobX works largely fine with Vue as long as you don't need libs that rely on Vue's observables.

It's my preferred go-to for Vue and React. Also opens the interesting possibility of supporting React and Vue components off the same stores..

> and the state management ecosystem is fractured between vuex and pinia

What do you mean fractured? They official recommend Pinia: https://vuejs.org/guide/scaling-up/state-management.html#pin...

> Storybook 'out of the box' is broken and doesn't work at all (unable to resolve '@/...' imports). It's been painful.

So you're blaming Vue because of bad experience with storybook?

https://v1.test-utils.vuejs.org/guides/#using-with-typescrip...

Follow all the steps.

    $ jest
    Error: Cannot find module 'vue-template-compiler'*

test-utils is a first party package.

My experience is the same across the ecosystem; 3rd party packages, 1st party packages. My 'Out of the box' experience is:

It doesn't work unless you screw around and manually patch things.

There's good things too, but this comment:

> I am not googling days to fix tooling issues

Resonates with my experience at 0%. I don't care who's fault it is, the tooling experience has been bad.

(* no, I really did follow all the steps -> https://stackoverflow.com/questions/65790642/test-suite-fail..., it's just broken)

Reply on news.ycombinator.com