Skypack version of vue-demi imports vue 2 but sets isVue3 to true

https://cdn.skypack.dev/-/vue-demi@v0.11.0-TmCmtDOAoOKuMLLEdJI0/dist=es2020,mode=imports/optimized/vue-demi.js

export * from "/-/vue@v2.6.14-ZwqBV9vu181DzQDewEXR/dist=es2020,mode=imports/optimized/vue.js";
import * as vue from "/-/vue@v2.6.14-ZwqBV9vu181DzQDewEXR/dist=es2020,mode=imports/optimized/vue.js";
export {vue as Vue};
var isVue2 = false;
var isVue3 = true;

[sibbng]

Since Skypack doesn’t have any way to override package versions (query variables etc.) I would suggest using jspm and import maps. vue-demi’s functionality comes from it’s post install hook which is where controls your vue version. In browser doing something like that possible with import maps.

I’m pretty sure you are not working on anything serious, and neither I do. That because I had experienced @vueuse/core + reactivue previously to see how vue-demi works in browser. Here it is: https://focused-williams-cf307d.netlify.app/ You can do CTRL+U for source code. I linked vue to reactivue in this example but in your case you can simply link it to vue 3. For generating import maps https://generator.jspm.io/ could help.

The least thing we could do is to release 3 versions at the same time - vue-demi@latest vue-demi@v2 vue-demi@v3. But not sure if it’s worth it at the current stage.

It will also require packages (fluent-vue, @vueuse/core etc) to release under 2 different tags. Since vue-demi isn’t supposed to be used in that way it would be an unnecessary effort.

[antfu]

The least thing we could do is to release 3 versions at the same time - vue-demi@latest vue-demi@v2 vue-demi@v3. But not sure if it’s worth it at the current stage.