Skip to content
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

Cache extension manifest files #28331

Closed
jrieken opened this issue Jun 9, 2017 · 6 comments
Closed

Cache extension manifest files #28331

jrieken opened this issue Jun 9, 2017 · 6 comments
Assignees
Labels
extensions Issues concerning extensions on-testplan perf-startup plan-item VS Code - planned item for upcoming
Milestone

Comments

@jrieken
Copy link
Member

jrieken commented Jun 9, 2017

We have seen some performance report about slow extension scanning and registering. This is the umbrella item which we use to track this.

@jrieken jrieken added extensions Issues concerning extensions perf labels Jun 9, 2017
This was referenced Jun 9, 2017
@jens1o
Copy link
Contributor

jens1o commented Aug 25, 2017

is this going to be handled in august release?

@sandy081
Copy link
Member

@jens1o No

@sandy081 sandy081 added this to the Backlog milestone Aug 28, 2017
@jens1o
Copy link
Contributor

jens1o commented Aug 28, 2017

😢

@shanalikhan
Copy link

shanalikhan commented Nov 21, 2017

Explore caching the package.json files of installed extensions

In iteration plan.
So Code will generate the extension.json file itself and to export / from API and CLI to setup extensions.

It would be great help for my Settings Sync !

@sandy081
Copy link
Member

sandy081 commented Dec 4, 2017

@alexandrudima FYI here is the issue referring to scanning extensions.

@alexdima alexdima changed the title Extension scanning slow? Cache extension manifest files Dec 4, 2017
@alexdima alexdima added the plan-item VS Code - planned item for upcoming label Dec 4, 2017
@alexdima alexdima modified the milestones: Backlog, November 2017 Dec 4, 2017
@alexdima alexdima closed this as completed Dec 5, 2017
@alexdima
Copy link
Member

alexdima commented Dec 8, 2017

Starting with November, the extensions manifest files (package.json) will be cached under the user data dir, in a folder called CachedExtensions. There will be a file named builtin (for a cache of the built-in extensions) and a file named users (for a cache of the user installed extensions)

@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
extensions Issues concerning extensions on-testplan perf-startup plan-item VS Code - planned item for upcoming
Projects
None yet
Development

No branches or pull requests

5 participants