Vue 3 Plan (Recommendations)

[arpowers]

Hey guys,
Is there is a plan regarding this plugin and Vue3?

Tried out v3 this weekend and this plugin was one of the sticking points as its integrated into the next Factor (Headless CMS)...

Primarily there are issues with installation and types due to the changes around Vue > createApp and so on...

[pimlie]

Hey, I have been working on vue-meta v3 for some while now but am not yet ready to release an alpha yet. You can track some of my work here (mostly the new API) but everything is still under heavy development so changes will happen ;)

[arpowers]

Looks nice, that's a good standard API for the composition stuff. Thanks, @pimlie!

Appears that production use for Vue 3 is gonna take a LOT longer (~12 months?) when you consider that all the libraries are going to have to catch up.

[arpowers]

@pimlie just a request, but would it be possible to get an alpha that has the "old" object-based API as well as new Vue 3 types.

Happy to wait on composition API stuff, but the other stuff is blocking our migration to Vue 3. If there is a way I could contribute I'd be happy to do it.

[pimlie]

Hey, I have been thinking about this but I'd rather not have to spent time supporting two versions for Vue v3. It isnt the time developing a vue-meta v2-based Vue3 version what worries me, it worries me much more that I then also have to support that for the coming time. And that would only take time away from developing a good/proper revamp of vue-meta for v3. Im hopeful I will be able to release an alpha in a month or so. It will for sure not take 12 months ;)

[arpowers]

Great! Excited to see it. As a thought, I HIGHLY recommend you don't underestimate the importance of backward compatibility.

If you plan on changing the API completely, you might as well start a new plugin rather than iterate this one.

How do I know this? My old company had 60k paying customers, I made this mistake.

[pimlie]

I fully agree with you, the whole discussion about the composition api showed this too.

That said, we cant deny that the current approach in vue-meta is somewhat flawed. And Vue3 is giving us new possibilities we didnt had in Vue2. It would be stupid to not use those possibilities and/or fix those flaws just for backwards compatibility.

Ofc I will try to maintain as much backward compatibility as possible, but cannot promise 100%. My main goal is to at least support the old data structure

[ux-engineer]

@pimlie also please take into account this new cool syntax with SFC Script Setup! 😎

[pimlie]

@ux-engineer Hey thx, but as far as I am aware thats just syntax sugar for Vue3's setup method? Or is there more to it? If not, then we will already support it (see the next branch link above, the vue-router example in that branch shows the new api)

[ux-engineer]

@pimlie that's correct, it is just an another way of writing code with Composition API. I should have defined my comment more in saying that we would like see the final examples in docs to include also this cool syntax 😋

Already glanced through your next branch's example...looking good so far 👍

I hope you are getting this new version out soon after Vue 3.0 release. Currently there are a few bottleneck packages that we need to wait for to support Vue 3 before we can go through the upgrade process ourselves... In our case it's mainly with Bootstrap-Vue, which have told they will release support 'a few days' after 3.0 comes out.

[pimlie]

Yeah, me too. Was writing tests yesterdays but ran into an issue with merging arrays which I need to look into. Was trying to omit that vmid/hid stuff up to now but have to add that back for backwards compatibility. But working with arrays is just a pain when you are trying to merge them like vue-meta does, hence why the vmid property exists atm.

For the rest the biggest missing features atm are:

• ssr support (shouldnt be that hard to add)
• onload + callbacks (might postpone this after first release)
• once (might postpone this after first release)
• skip (might postpone this after first release)
• docs

[cricketthomas]

@pimlie really excited for vue 3 support. Is there a way we could test out the next branch version?

[ux-engineer]

Vue 3.0 is stable now, jej! 🎉

How is the upgrade plan looking like?

[redrbrt]

Vue 3.0 is stable now, jej! 🎉

How is the upgrade plan looking like?

Following this thread, waiting excited the next release