Closed freezboi closed 1 year ago
Darwin
v16.15.1
2.16.0-27616340.013f051b
yarn@1.22.10
webpack
bridge
head
css
plugins
components
buildModules
modules
axios
vuetify
build
typescript
vite
serverHandlers
devServerHandlers
@nuxtjs/axios@5.13.6
()
@nuxtjs/vuetify@1.12.3
@pinia/nuxt@0.3.0
@nuxt/bridge@3.0.0-27628751.3df21c7
https://stackblitz.com/edit/github-er4gxj?file=pages%2Findex.vue
https://v3.nuxtjs.org/guide/directory-structure/plugins#automatically-providing-helpers
It seems that type inference does not work properly when using it in a component after creating a custom plugin by following the guide in the link. In the case of the newly created $first plugin, the type is any.
No response
I guess this issue is related to https://github.com/nuxt/bridge/issues/539.
This issue was resolved at https://github.com/nuxt/bridge/issues/539.
Environment
Darwin
v16.15.1
2.16.0-27616340.013f051b
yarn@1.22.10
webpack
bridge
,head
,css
,plugins
,components
,buildModules
,modules
,axios
,vuetify
,build
,typescript
,vite
,serverHandlers
,devServerHandlers
@nuxtjs/axios@5.13.6
()
,@nuxtjs/vuetify@1.12.3
,@pinia/nuxt@0.3.0
,@nuxt/bridge@3.0.0-27628751.3df21c7
Reproduction
https://stackblitz.com/edit/github-er4gxj?file=pages%2Findex.vue
Describe the bug
https://v3.nuxtjs.org/guide/directory-structure/plugins#automatically-providing-helpers
It seems that type inference does not work properly when using it in a component after creating a custom plugin by following the guide in the link. In the case of the newly created $first plugin, the type is any.
Additional context
No response
Logs
No response