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

vsce package is inefficient #80

Closed
petervdonovan opened this issue Aug 28, 2022 · 5 comments
Closed

vsce package is inefficient #80

petervdonovan opened this issue Aug 28, 2022 · 5 comments
Labels
good first issue Good for newcomers

Comments

@petervdonovan
Copy link
Contributor

This algorithm is causing problems for us. The build has been super slow for a long time, and this slowness is totally unnecessary. Basically vsce package indexes directories that are ignored in .vscodeignore -- in particular, the lingua-franca submodule -- only to filter them out afterward. I was prompted to investigate this when I finally started getting an Allocation failed - JavaScript heap out of memory error just by running npx vsce ls.

We need to either fix things on our end by not using the submodule, or else try to fix things on vsce's end.

@lhstrh
Copy link
Member

lhstrh commented Aug 31, 2022

What would be a reasonable alternative to using a submodule? In any case, we need to build the language server. Providing a fix to vsce sounds reasonable, but I'm afraid it might take a while for it to get merged?

@petervdonovan
Copy link
Contributor Author

petervdonovan commented Aug 31, 2022

Given that there are so many other things in progress that do not involve this issue, and that this issue does not affect the quality of the artifact, I would personally prefer to defer action on this.

We can depend on a fork of vsce if it comes to that; I might prefer maintaining a fork over having to change the build and release workflows, since those aspects of our code base are the most time consuming to test.

Edit: To answer directly, I do not know what we would do without using a submodule. We did not originally use a submodule, but there is a reason why we switched.

@lhstrh
Copy link
Member

lhstrh commented Aug 31, 2022

Sounds reasonable! If the fix is quick (which it appears to be), then it might be worth submitting a PR for vsce soon though. There is a chance that it will be adopted relatively soon, which would simplify things for us going forward.

@petervdonovan petervdonovan added the good first issue Good for newcomers label Apr 18, 2023
@lhstrh
Copy link
Member

lhstrh commented May 6, 2023

Is this still a thing? I think the build is pretty fast now? Shall we close this?

@petervdonovan
Copy link
Contributor Author

I do not know but I saw that you updated vsce today. I'm fine closing this since it is only a developer-facing issue. If it becomes a problem for me again in the future then I'll just fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants