-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
ATA puts types in $HOME/Microsoft #16318
Comments
Steps to reproduce:
It only happens for the first JS file that is opened. Could be a bug, too. |
I guess this is from the automatic typings acquisition in recent versions of TypeScript. @Instagit Are you saying the folder is under |
@chrmarti is correct - this is location of global cache for acquired type declarations. These files are downloaded on user machine to power JavaScript intelligence and never uploaded anywhere. |
Now that you mention this I have this too. We should absolutely not be putting the types in @vladima this is actually quite bad imo, is this a purely upstream problem? |
This issue was moved to microsoft/TypeScript#12674 |
Let's keep this open on vscode to track it. I'd like to mention the fix in release notes when it comes. |
This is going into TypeScript 2.2, so we will not be picking it up in VSCode 1.8. You can install a TS 2.2 insiders build to your workspace to work around this for now. |
I have yet to find out how to reproduce this, but VS Code creates a Microsoft/TypeScript/node_modules/ directory with the types-registry npm module in it in the home directory.
The package readme says
I never set anything to be shared or published. So what exactly is this and what does it do?
The text was updated successfully, but these errors were encountered: