Vue 2 & 3 compat

[jacogr]

Not sure how that story plays out - when just bumping the deps to 3.x we have issues. If not compatible, need some way to support both.

[tinydjp]

Hi @jacogr may I know is there any plan for the upgrade?

[jacogr]

It needs to be done, which is why it is logged. :)

PRs for a Vue 3.x version that replaces Vue.extend with createComponent always welcome.

When releasing it it will mean that we will bump to version 2.0 here and probably provide the old/current version as @polkadot/vue2-identicon (so users can use either version, but the default being the one on the latest Vue 3 framework)

[dcolley]

In my experience vue2 and vue3 are different enough to require different repos / branches

[jacogr]

It is a bit out of my wheelhouse... but if possible, would prefer to have package/vue2-identicon and packages/vue-identicon for vue3. They do operate independently inside packages/*.

If not at all possible.... well, then I guess The 2.x series would be for vue 2 and vue 3 will need a major bump. (It would need a major bump when renaming anyway, so with either option that is a given)

[vikiival]

It is possible to use Vue-demi

[dcolley]

I would not recommend tracking different versions of vue in your code - that's what branches are for.

[polkadot-js-bot]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.