TypeScript errors not showing after upgrading VSCode to v1.39
See original GitHub issueInfo
- Platform: macOS 10.15
- Vetur version: 0.22.4
- VS Code version: 1.39.1
- TypeScript version: 3.6.4
Vue file: TS + SCSS (modules)
Problem
After a few minutes, VSCode stops displaying errors and hover tooltips for TS part of .vue
component files. Output logs for vue language server are empty. Window reloading helps but only for 5-10 minutes.
I think it started to happen after upgrading VSCode to v1.39
. For plain .ts
files it still works.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Refreshing errors in VSC after installing typings - Stack Overflow
I finally figured this out. Visual Studio Code offers a command for reloading the window and another for reloading the project.
Read more >Visual Studio Code Tip: Show TypeScript Errors in Entire Project
Now I can press ALT+SHIFT+B , wait for TypeScript to finish the compilation and then start pressing ALT+END to navigate to the errors...
Read more >TypeScript Programming with Visual Studio Code
TypeScript is a typed superset of JavaScript that compiles to plain JavaScript. It offers classes, modules, and interfaces to help you build robust...
Read more >VS Code 1.7.1.2 and Plots.jl not working - Julia Discourse
I'm using Julia v1.8.1 and Plots v1.34.3. Note that plotting using the REPL outside VSCode works fine. Edit: adding the GR package, changed...
Read more >VS Code: You don't need that extension - Rob O'Leary
JavaScript > Update Imports on File Move: Enabled : "Enable/disable automatic updating of import paths when you rename or move a file in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Downgrading to Vetur
v0.22.3
resolves the problem.Thank you for filing this issue. Let’s track it on #1449.