pinia-plugin-persistedstate VS vueuse

If you use a standard Pinia store, you can use plug-ins. For example, you can use pinia-plugin-persistedstate to let the user start each new session where they left off. Or you can use pinia-orm to simplify handling large amounts of tabular data.

How about this plugin, then?: https://github.com/prazdevs/pinia-plugin-persistedstate.

When your application starts, fill your Pinia/Vuex store with data from the user's previous session. This is done automatically by pinia-plugin-persistedstate or the Vuex equivalent.

pinia-plugin-persistedstate: keeps your Pinia store synced with the user's browser localStorage. In other words, if your user closes their browser and then returns to your Vue app later, they will have the same state as when they left.

You also mentioned that the positions should be stored in localStorage. I would store the positions in Pinia, and then add the pinia-plugin-persistedstate plug-in. It's one import statement and one line of code to add that plugin, and then your Pinia state is automatically persisted in localStorage. It beats having to write and troubleshoot the storage logic yourself.

I've used the pinia-plugin-persistedstate package and has worked fine for me.

I have a Vue 3 / TypeScript app that uses a combination of Firebase, Pinia, Vue Concurrency, and the Pinia Persisted State Plugin.

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.