Skip to content

ATA puts types in $HOME/Microsoft #12674

Description

@mjbvz

From Instagit on December 1, 2016 10:38

  • VSCode Version: 1.7.2
  • OS Version: Ubuntu 16.04

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

This is the source code for the types-publisher service, which publishes the contents of DefinitelyTyped to npm.

I never set anything to be shared or published. So what exactly is this and what does it do?

Copied from original issue: microsoft/vscode#16318

Activity

  1. mjbvz commented on Dec 5, 2016

    @mjbvz
    Author

    From Instagit on December 2, 2016 9:26

    Steps to reproduce:

    1. open VS Code
    2. open any JavaScript file

    It only happens for the first JS file that is opened. Could be a bug, too.

  2. mjbvz commented on Dec 5, 2016

    @mjbvz
    Author

    From Christof Marti (@chrmarti) on December 2, 2016 19:23

    I guess this is from the automatic typings acquisition in recent versions of TypeScript. Instagit Are you saying the folder is under ~/Microsoft?

  3. mjbvz commented on Dec 5, 2016

    @mjbvz
    Author

    From Vladimir Matveev (@vladima) on December 2, 2016 20:12

    Christof Marti (@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.

  4. mjbvz commented on Dec 5, 2016

    @mjbvz
    Author

    From Christof Marti (@chrmarti) on December 2, 2016 23:7

    Vladimir Matveev (@vladima) What are the paths that are used for this cache on the different platforms? I think on Linux it might make sense to used a folder name with a leading '.' to hide it from default ls and file explorer behavior - like other tools do. /cc Daniel Imms (@Tyriar)

  5. mjbvz commented on Dec 5, 2016

    @mjbvz
    Author

    From Daniel Imms (@Tyriar) on December 2, 2016 23:22

    Now that you mention this I have this too. We should absolutely not be putting the types in ~/Microsoft. $XDG_CACHE_HOME/typescript would probably make the most sense, where $XDG_CACHE_HOME defaulting to $HOME/.cache if it is not defined as per the XDG Base Directory Specification. I'm proposing typescript/ instead of microsoft/ to prevent potential future conflicts.

    Vladimir Matveev (@vladima) this is actually quite bad imo, is this a purely upstream problem?

  6. mjbvz commented on Dec 5, 2016

    @mjbvz
    Author

    I believe the location of the typings install directory is coming from TypeScript, so I've moved the issue from the vscode repo to here.

  7. locked and limited conversation to collaborators on Jun 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugA bug in TypeScriptDomain: LS: TSServerIssues related to the TSServerFixedA PR has been merged for this issueVS Code TrackedThere is a VS Code equivalent to this issue

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions