We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
defineComponent
any
https://stackblitz.com/edit/github-heoruj?file=defineComponent.ts
Even with bridge.capi: true, the aliases for the legacy @nuxtjs/composition-api are still defined in .nuxt/tsconfig.json.
bridge.capi: true
@nuxtjs/composition-api
The return value of defineComponent in there is any, so the types for Vue components are not inferred correctly.
bridge/packages/bridge/src/runtime/capi.legacy.ts
Lines 220 to 227 in 3c40b3f
It looks like this could fix the issue. What do you think?
import {defineComponent as defineComponentVue } from "vue" export const defineComponent: typeof defineComponentVue = (options) => { if (!('head' in options)) { return options } return { ...options, ...getHeadOptions(options) } }
No response
The text was updated successfully, but these errors were encountered:
I think the solution described in the description is a good one!
Sorry, something went wrong.
Fixed at #994
No branches or pull requests
Environment
Reproduction
https://stackblitz.com/edit/github-heoruj?file=defineComponent.ts
Describe the bug
Even with
bridge.capi: true
, the aliases for the legacy@nuxtjs/composition-api
are still defined in .nuxt/tsconfig.json.The return value of
defineComponent
in there isany
, so the types for Vue components are not inferred correctly.Additional context
bridge/packages/bridge/src/runtime/capi.legacy.ts
Lines 220 to 227 in 3c40b3f
It looks like this could fix the issue. What do you think?
Logs
No response
The text was updated successfully, but these errors were encountered: