buefy VS vue-cli

I looked into Buefy, which has great and accessible source code btw, and my hunch was correct. See line 184 at this link: https://github.com/buefy/buefy/blob/dev/src/components/carousel/CarouselList.vue

Buefy: A lightweight UI library that provides a range of customizable UI components, including forms, buttons, and navbars.

Back in the day I used Buefy https://buefy.org/ which is a Vue version of Bulma. I like it, I'd say it was easy to implement and I could change the style a bit without too many lines of code.

I'm learning Vue and today noticed something I hadn't seen before, by Buefy component templates, namely hash-prefixed attributes on template tags e.g.

Encountered this issue as we're looking into solutions for migrating a Vue 2 + Buefy codebase over to Vue 3. The maintainer is actively working on Oruga, which for the most part, has a very similar api to Buefy components and is pretty close in terms of component parity. I only found out about Oruga through this pinned issue in the Buefy repo.

That will render any Vue components referenced within the content returned from the API. In my case, it contained Buefy component references e.g.:

I like Bulma and I've used it on most recent projects. It feels lighter and easier to customize than Bootstrap. Buefy is vue components based on Bulma. It's pretty good, but lately I've been using Livewire.

Personally I don't like either. Bootstrap seems too bloated and cookie-cutter, and Tailwind is inline styles and clutter. Lately I've used Bulma (CSS framework) and Buefy (Bulma + Vue) on a couple of projects. I also like the look of Pure CSS, but I haven't used it.

It seems that the good UI frameworks are only available for Vue 2 at present. Bootstrap (Bootstrap-vue), Semantic UI (Semantic UI Vue), Bulma (Buefy), Material (Vuetify) all only support Vue 2.

7 - Buefy

Immerse yourself in the official Vue CLI documentation for a deeper understanding.

Security would be a useful benefit/section to add to this post:

A.) If maintainers of your dependencies edited an existing version.

B.) If your dependencies did not pin their dependencies.

For instance, if you installed vue-cli in May of last year from NPM with --prefer-offline (basically the same as checking in your node_modules), you were fine. But because vue-cli doesn't pin its dependencies ("node-ipc"), installing fresh/online would create WITH-LOVE-FROM-AMERICA.txt on your desktop [1], which was at the very least a scare, but for some, very problematic.

[1] https://github.com/vuejs/vue-cli/issues/7054

Vue CLI documentation: https://cli.vuejs.org/

An interesting fact is that this dependency was used in vue-cli.

Vue CLI 3

Open issue for half a year https://github.com/vuejs/vue-cli/issues/7234

Vue CLI (command-line interface), which is used to install and create the main Vue framework libraries and third-party plugins.

Is there a reason you've used the old Vue CLI though, with webpack and babel?Imho you're missing a lot not using Vite... npm init vue@latest (create-vue) is the recommended way to scaffold a new Vue app, Vue CLI is in Maintenance Mode

The official Vue CLI UI is made with Vue + Apollo GraphQL. You'll know it when you run vue ui in your terminal. - https://github.com/vuejs/vue-cli/tree/dev/packages/%40vue/cli-ui

Both Vue.js and React have their own set of tools and libraries to help developers build and maintain their applications. Vue.js has Vue CLI and Nuxt.js, while React has Create React App and Next.js.