-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Get an error from vue-tsc
after change app.vue
and save.
#17680
Comments
Tried your exact project folder that you supplied. Same thing (works). |
sorry i forgot to push... |
I saved the file (with and without changes), but it works as expected. |
on windows? The old Any other suggestions? |
Tested on macos. Will be able to test on Windows later today. |
Tested on a Windows 11 Home too and could not reproduce. Used Git Bash as shell (so not on WSL). :( |
Can you use the "regular" terminal instead of the VSCode one pls? Who knows... |
One more thing: I am on Node 20, not 22. Can you test with v20 also, pls? |
|
There are some things wrong in npx vue-tsc -w then [11:09:59 PM] File change detected. Starting incremental compilation...
error TS6053: File 'D:/workspace/quasar/src/pages/IndexPage.vue' not found.
The file is in the program because:
Matched by include pattern '.quasar/./../**/*' in 'D:/workspace/quasar/tsconfig.json'
[11:09:59 PM] Found 1 error. Watching for file changes.
|
I found renaming the file can solve the problem temporarily. |
I have to disable ...
[
'vite-plugin-checker',
{
vueTsc: false, // set to false
eslint: {
lintCommand: 'eslint -c ./eslint.config.js "./src*/**/*.{ts,js,mjs,cjs,vue}"',
useFlatConfig: true,
},
},
{ server: false },
],
... |
What happened?
Get an "not found" error after file changes watching. like,
What did you expect to happen?
It SHOULD work correctly without any errors.
Reproduction URL
https://github.com/lichaozhy/quasar-issue
How to reproduce?
./src/App.vue
Flavour
Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)
Areas
TypeScript Support
Platforms/Browsers
Chrome
Quasar info output
Relevant log output
Additional context
No response
The text was updated successfully, but these errors were encountered: