buefy VS svelte-i18n

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

Yeah I'm just using svelte-18n

Make sure you have Node.js and npm installed. It's best, if you have some experience with simple HTML, JavaScript and basic Svelte, before jumping to svelte-i18n.

There are some great i18n libraries which can be used together with SvelteKit, such as svelte-i18n, typesafe-i18n or svelte-intl-precompile. However, a month ago, I decided to create my own, modular and lightweight one, because i was missing some features like dynamic translations load (load translations for visited pages only), custom translation sources (e.g. external API) or component scoped translations, etc...

I had reasonable success with https://github.com/kaisermann/svelte-i18n in one of my pet projects.

With the svelte-i18n library internationalization of a Svelte / Sapper apps has gotten a lot better, but there has been an omission in solutions for routing languages (despite long discussions). I would like to share our solution for making internationalized routing: