PraZ

given how the plugin is and how simple it has to stay, this will no be implemented. however you can still implement this "flatten" style method in your own storage.setItem...

Posting my thoughts in this PR so I dont forget it: Considering offering compatibility with as many storages as possible through drivers, basically interfaces between any storage and the plugin's...

Closing this for now. I'll wait for the official release of Nuxt to start working on a serious and consistent solution 💤

So far, i can only think of browser storages like localStorage, but it is client only. Do you need the SSR full compatibility ?

I could only think of splitting the store into multiple cookies, cause i dont see many alternatives compatible with both client and server side 🤔

I dont know what data structure you store in Pinia, but if you have unsplittable properties/chunks heavier than 4KB, I dont think they belong in the store. Maybe some cached...

Ive been trying to play around alternative solutions that dont interfere with the plugin, but it's not very easy. Technically, cookies should not have a limited size (from the cookies...

Technically it should, but I need to look into when the cookie and keys are parsed and created, that could explain your problem.

You may want to open another issue with a proper reproduction repo/stackblitz to make it clearer, it's moving away from the main concern of this issue :)

As the solution proposed in #99 works, you can use it to create your own storage deriving nuxt's useCookie (or any sort of cookie) and pass it to the plugin....