Is your feature request related to a problem? Please describe.
While trying to make Vue-Apollo plugin work nicely with vite & Vue 3, I've runned into an issue with how the generated code handles imports.
Since Native ES modules handles imports differently, those lines causes issues
import * as VueApolloComposable from '@vue/apollo-composable';
import * as VueCompositionApi from '@vue/composition-api';
Describe the solution you'd like
It should be something like this instead.
import VueApolloComposable from '@vue/apollo-composable';
import VueCompositionApi from '@vue/composition-api';
Describe alternatives you've considered
The vue-apollo codegen plugin could either allow to completly disable the imports and use the plugin add to manually write imports or a property like prioritizeDefaultImports that would just use the default import instead of an namespace import.
I'd be more than happy to offer my help on any implementation to fix this issue. 😀
Is your feature request related to a problem? Please describe. While trying to make Vue-Apollo plugin work nicely with
vite
& Vue 3, I've runned into an issue with how the generated code handles imports.Since Native ES modules handles imports differently, those lines causes issues
Repo demonstrating the issue
Describe the solution you'd like It should be something like this instead.
Describe alternatives you've considered The
vue-apollo
codegen plugin could either allow to completly disable the imports and use the pluginadd
to manually write imports or a property likeprioritizeDefaultImports
that would just use the default import instead of an namespace import.I'd be more than happy to offer my help on any implementation to fix this issue. 😀