-
-
Notifications
You must be signed in to change notification settings - Fork 996
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
Vue3 Plugin import resolves to any in Nuxt 3 #2071
Comments
I'm not sure if this is a misusage of the Nuxt module in Pinia, a regression in Nuxt, or something else. Feel free to pick it up and propose a Pull Request! |
I'm not very aware of how the modules work, but do you think it has something to do with the way the package is built ? declare const _default: any;
export default _default; |
Yes, this seems like an issue with the module builder to me. |
It needs to be updated here. I think it’s still using siroc |
Happy to pick this up. |
Feel free! |
Since I see |
* fix casing for import * convert parse-message to TypeScript * explicit typing for injected Pinia until vuejs/pinia#2071 is fixed * loading payload via fs, not dynamic import * explicit non-null assertion * typings for generateRoutes
Reproduction
https://stackblitz.com/edit/nuxt-starter-4b7cfk?file=app.vue
Steps to reproduce the bug
Install
pinia
and@nuxt/pinia
, run the dev server and let it generate the typings for the project.Go to
.nuxt/types/plugins.d.ts
See the following block:
Visit the
../../node_modules/@pinia/nuxt/dist/runtime/plugin.vue3
file:Expected behavior
The property
$pinia
should be visible in the returned object ofuseNuxtApp()
Actual behavior
The vue 3 plugin type definitions are outputted as any
Additional information
No response
The text was updated successfully, but these errors were encountered: