vue-i18n VS vueuse

vue-i18n

Your working in a team on a software project. The user interface needs to support multiple different languages, so your team either picks an open source tool for this (next-translate, typesafe-i18n, vue-i18n, etc), or depending on your development framework, internationalization features might be baked right in (IOS, Android, AngularJs, etc).

You want internationalization or i18n support. I use this: https://kazupon.github.io/vue-i18n/ which is the official plugin.

Kazupon is a well-known developer at Vue.js. He is also the creator of Intlify, known for its contribution to the software internationalization space, which has created an internationalization plugin for Vue.js known as Vue I18n.

I use vue-i18n and it works well for my web app. It took a little bit of fiddling to get it to work with the Composition API, to build a language switcher component, and to set up lazy loading of language files. I followed their examples for Locale changing and Lazy loading translations, and I'm happy with the result.

This source code was implemented based on Vue I18n official Guide and Issues on its Github repository.

My opinion: Vue, specifically the Vue 3 Composition API. Most of your app state should come from computed() values. Bookmark https://vueuse.org and come back to it often. Go through VueUse's source (the docs for each function link to their source): you'll be surprised at how simple most of it is, and it stands as documentation of best practices for using the composition API in general.

Now, let’s talk about Vue! Once again, we’ll use an external library to handle dark mode simply and quickly. In this case, the library is called VueUse, and you can install it using the command npm i @vueuse/core --save.

Great library. Could use some improvements as said by other (tree shaking, add jsdocs, etc…). Just a quick reminder for the vuejs devs out there we have https://vueuse.org/

Yeah, I figured useHooks was created without knowing about VueUse, but thought they might have become aware of it sense then. It makes sense, because though the code is heading in the direction of VueUse in terms of being maintained and well rounded, the structure of useHooks is quite a bit different. It has the code alongside the Markdown: https://github.com/vueuse/vueuse/tree/main/packages/integrat...

Demo: https://github.com/vueuse/vueuse/blob/main/packages/core/useWebNotification/demo.vue

Also take a look at https://vueuse.org/ which might save you some lines :)

For what it's worth my timeframe is very similar to yours! Started in 2019, no React / Angular. I think looking at great codebases like [VueUse](https://github.com/vueuse/vueuse) shows off the best of composition API.