-
-
Notifications
You must be signed in to change notification settings - Fork 390
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
No tsconfig in newly created vue file #3329
Comments
This comment was marked as outdated.
This comment was marked as outdated.
There is a breaking change in v1.8.2 :( no longer parse vue files outside tsconfig include option to avoid TS performance concerns (#3326) |
I used the "include" attribute to include the vue file in the "src" directory. This problem only occurs in new files. Previous files or overloaded vscode will return to normal. |
Let's keep it open to investigate further |
Any newly created file fails for me. Vue file or plain TS file. Using Volar 1.8.3 in takeover mode. Only work around is to reload the window. Restarting Volar only is not sufficient. |
any solution |
it seems like that, extension can not found the files created by copy or |
Should it work now? |
No, still show "No tsconfig" |
It's a bit disgusting,How to solve it? |
Can someone check which version introduced this regression? |
Any progress, guys? |
@aleksey-hoffman It seemed to be a display issue, shouldn't affect language support. |
@so1ve the problem is, when you create a new component file, vscode doesn't show autocomplete suggestions for it (imports and template tags). So you have to restart vscode every time you create a new file or import and write tags for all new components manually Perhaps the problem is caused by vscode and not the LSP, I'm not sure |
Nah! This is quite annoying. I'm looking for a solution |
I have some info that may be useful. I created a repo to reproduce the bug, follow the readme to see how reproduce the bug: This repo is very similar to my real project that has this bug and I using nuxt 3 in this repo. Looks like when I add a local module the bug start to happened. One thing I notice is that if you comment on this part of tsconfig.json, the tsconfig.json is detected by vscode normally And another note is that nuxt will add these paths to the extended tsconfig.json when a new module is detected So I guess the bug is related to tsconfig.json exclude, include paths, or it could be and invalid tsconfig.json since theses files do not exists |
me too !Is there a way to fix this? |
For anyone that has a similar problem to me related to nuxt, looks like it was a problem with auto generated tsconfig.json issue: nuxt/nuxt#23794 The workaround for now is to register modules manually // nuxt.config.ts
export default defineNuxtConfig({
modules: ["modules/my-local-module"]
}) |
I am using vue language server with helix editor.
creating new files doesn't add them to the auto import hint, and I have to restart the server all the time for the file to be noticed by it |
I have also encountered the same problem and do not know how to solve it. I have provided the following minimal reproducible cases, hoping to provide some help。 repo:https://github.com/rennzhang/vue3-ts-error-report You can follow these steps to repeat
<template>
<div></div>
</template>
<script lang="ts" setup>
let a = ref(1);
</script>
<style scoped lang="less"></style> The following error will occur
|
This still happens to me, for every single new vue file, I need to restart VSCode, otherwise nothing will work inside that file, so annoying. |
same issue :(( |
I'm having the same issue here, not sure why this was closed. |
This is still happening. No Intellisense, no definitions. I have to restart the TS server every new file |
There is a ts problem in my project. Every time the newly created vue file is displayed "No tsconfig", the tsconfig will be obtained normally after reloading using vscode.
The text was updated successfully, but these errors were encountered: