-
-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with @vue/composition-api
resolution
#212
Comments
@vue/composition-api
resolution@vue/composition-api
resolution
I would suggest additionally alias any other variant of imports from This issue indeed is broader especially in conjunction with externals and also might happen for |
Is this now indeed resolved? I just got the following error
using latest bridge + vite. Can be fixed by adding |
@tobiasdiez I think it's an issue with the version of |
That might be indeed the case and there is already a PR for apollo-composable upgrading vue-demi vuejs/apollo#1278. Instead of only adding more noise, let me also use the opportunity to thank you a lot for all the work you guys are putting into nuxt! Especially your last PR about the esm docs was super helpful! |
Describe the bug and expected behavior
Libraries may resolve their own version of
@vue/composition-api
. For example,vue-demi
does this: vueuse/vue-demi#105Any resolved version will fail if transpiled (e.g.
@vue/composition-api/dist/vue-composition-api.esm.js
gets resolved - because of the alias we set - to@vue/composition-api/dist/vue-composition-api.mjs/dist/vue-composition-api.esm.js
.Moreover, if not transpiled, if the resolved version is not what we use (the
.mjs
version), the composition API plugin will not be successfully enabled and libraries that use (for example)vue-demi
will fail confusingly.It is possible to resolve by creating additional aliases in bridge/capi but wanted to raise as an issue before submitting PR as this is a broader ecosystem issue. (It will, for example, also affect
@nuxtjs/composition-api
and other community libraries.)cc: @antfu
The text was updated successfully, but these errors were encountered: