chore: bump @vue/composition-api, fix #244

[antfu]

fix #244

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/nuxt-community/composition-api/3e5g3fyrl
✅ Preview: https://composition-api-git-main.nuxt-community.vercel.app

[danielroe]

Thanks @antfu ❤️

[antfu]

Any idea why the test fails?

[danielroe]

@antfu Looking into it.

[danielroe]

@antfu It's erroring because Vue.set is now failing on reactive objects (but only on SSR):

const a = reactive({})
Vue.set(a, 'prop', 'value')

See https://codesandbox.io/s/wizardly-glitter-v9nd0?file=/pages/index.vue

I'll see if I can remove it from useMeta and then we should be good to go.

[danielroe]

@antfu - looks good to go from my point of view but I guess the question is whether you regard the changed behaviour of Vue.set as a bug or not.

[aaronhuisinga]

Thanks @antfu and @danielroe! Would love to see this merged so we can work out some of the bugs we're still dealing with!

[antfu]

@danielroe Bumped the version to beta.16 and changed Vue.set to set from VCA. Should work fine now. You would also want to use set instead of Vue.set for most of the cases in the future. 😉

[danielroe]

Fantastic - thanks so much for this ❤️

[bissolli]

Guys, not sure if it is something that we should be concerned of, but after this update I started getting this friendly error:

 WARN  in ./.nuxt/composition-api/index.js                   friendly-errors 11:08:50

"export '_set' (reexported as 'set') was not found in '@vue/composition-api'

[danielroe]

This warning should not appear in v0.13.0.