Vetur ignoring tsconfig.json from project when running VSCode in workspace mode
See original GitHub issueInfo
- Platform: Linux
- Vetur version: 0.11.7
- VS Code version: 1.20
Problem
Vetur ignores tsconfig.json in project (or at least the experimentalDecorators option) when running VSCode in workspace mode.
Reproducible Case
I used the nuxt TypeScript template from here and had the folder open in a workspace. I was simply getting this error message on decorators: Experimental support for decorators is a feature that is subject to change in a future release. Set the 'experimentalDecorators' option to remove this warning.
After some time i figured I might try without using the workspace so I opened the project directly and the error was gone. In addition I also tried placing the same tsconfig.json in the workspace directory which also worked.
I think vetur has no proper VSCode workspace functionality yet for finding the tsconfig.json.
Related issues
https://github.com/vuejs/vetur/issues/567 https://github.com/nuxt-community/typescript-template/issues/5
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (1 by maintainers)
Top GitHub Comments
I have the same issue and i found little workaround in a workspace mode! If you place your nuxt/frontend project on the top of workspaces tree then Vetur obviously read tsconfig from this first workspace and everything works without warnings/errors in .vue files.
I’m experiencing the same problem. If I just load up my project without a workspace everything works as expected. But the moment I load up my Vue project inside a workspace Vetur is not using the tsconfig.json file from the project.