You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once I added new types via @types (AKA DefinitelyTyped) modules, I started to see all sorts of info entries under the VS Code Problems tab trying to give me tips on TypeScript features that I hadn't marked as learned yet:
Doesn't seem like something you'd want to see by default.
I also couldn't get rid of these via exclude or skipLibCheck.
The text was updated successfully, but these errors were encountered:
Same here if I ctrl+click to see a type myself. Then the extension parses the .d.ts file and shows me all kinds of info which would be cool if it would go away when I close the .d.ts file but instead, it freezes things. TS stops working completely if I'm using volar in a vue project. Things get slow when using regular TS extension in a React project. But in both cases the problems tab stays full after closing the d.ts file.
Maybe a setting to enable or disable for node_modules ?
Once I added new types via @types (AKA DefinitelyTyped) modules, I started to see all sorts of info entries under the VS Code Problems tab trying to give me tips on TypeScript features that I hadn't marked as learned yet:
Doesn't seem like something you'd want to see by default.
I also couldn't get rid of these via
exclude
orskipLibCheck
.The text was updated successfully, but these errors were encountered: