Skip to content

Trim the size of the closures, they are _way_ too large. #209

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

Open
angerman opened this issue Feb 14, 2025 · 0 comments
Open

Trim the size of the closures, they are _way_ too large. #209

angerman opened this issue Feb 14, 2025 · 0 comments

Comments

@angerman
Copy link
Collaborator

This is going to need a bit of analysis, but currently the closures are hopelessly large, and we should trim them aggressively. We rely on a lot of GH runner cleanup to even make it work. This is not sustainable.

Maybe we should:

  • drop documentation
  • drop profiling libs? Make them re-downloadable?
  • drop excessive hls versions?
  • what else is in the closure?

Step 1 would need to be to just figure out what's in the dependency closure and take a good hard look if it needs to be in there. If not, why it's in there.

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

No branches or pull requests

1 participant