useStore not unwrapping MaybeRefOrGetter

[arnKo]

Describe the bug

The defaults argument of useStore is typed as MaybeRefOrGetter:

export function useStorage<T extends(string | number | boolean | object | null)>(
  key: string,
  defaults: MaybeRefOrGetter<T>,
  storage: StorageLike | undefined,
  options: UseStorageOptions<T> = {},
): RemovableRef<T>

However the value is not correctly unwrapped in line 148:

const data = (shallow ? shallowRef : ref)(defaults) as RemovableRef<T>

If using a getter function () => T as defaults, data will be: RemovableRef<() => T> instead of RemovableRef<T>.

Reproduction

https://stackblitz.com/edit/vitejs-vite-6bznlt?file=src%2FApp.vue

System Info

System:
    OS: Linux 5.15 Linux Mint 21.2 (Victoria)
    CPU: (8) x64 Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
    Memory: 19.58 GB / 31.19 GB
    Container: Yes
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.20.2 - /usr/bin/node
    Yarn: 1.22.10 - /usr/bin/yarn
    npm: 8.19.4 - /usr/bin/npm
  Browsers:
    Chrome: 117.0.5938.88
    Chromium: 117.0.5938.62
  npmPackages:
    @vueuse/core: ^10.4.1 => 10.4.1
    vue: ^3.3.4 => 3.3.4

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a VueUse issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.
• The provided reproduction is a minimal reproducible example of the bug.

[arnKo]

Additionally, using a computed as defaults results in a warning from vue when trying to set the data: Write operation failed: computed value is readonly

[jizai1125]

Upgrade @vueuse/core to the latest.