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
vue-component-meta: checker not working with tsconfig that uses references #3896
Comments
This is the expected behavior, project references should not affect the files included in tsconfig. To check Perhaps what you need is a checker manager that automatically finds a valid tsconfig for a .vue file (considering project references). It is possible to port the relevant logic from the vue language server. I don't want to give false hope, as this task requires a significant amount of work and I still have other pending tasks, so there is currently no schedule for implementation. |
Thank you, @johnsoncodehk, for your feedback. We've opted to specify the tsconfig.app.json path instead. I acknowledge that the proper approach is to pass a valid tsconfig. For now, in the workaround, we explicitly pass the tsconfig to use in the Storybook config file. Ideally, @larsrickert, we should create a lookup manager that automatically detects the first valid tsconfig in references. I'll take care of this part. |
👌 I was exploring this yesterday 😁 wondering if i'm in the right place ✌️ thanks for guidance |
When using
vue-component-meta
with atsconfig.json
that uses references (like the one that is provided by the official Vue starter), the checker will throw an error "Could not find main source file" and does not provide any meta.Versions
node: 20.10.0
typescript: 5.3.3
vue-component-meta: 1.8.27
vue: 3.4.19
@vue/tsconfig: 0.5.1
@tsconfig/node20: 20.1.2
Reproduction
Vue component:
vue-component-meta
Code:tsconfig.json
filetsconfig.app.json
file:tsconfig.node.json
file:The text was updated successfully, but these errors were encountered: