Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Bring package size down

See original GitHub issue

The size of the module is around 290MB’s because we ship standalone apps for

win-x64
osx-x64
linux-x64

This is because of a limitation on non-Windows that forces us to use a separate process to render GUIs.

We can possibly get this down by using AssemblyLoadContext.Default.Resolving and copying duplicate dlls to a shared location. We might be able to do a similar tactic with dlls that ship IN PowerShell itself.

Issue Analytics

State:
Created 4 years ago
Reactions:8
Comments:8 (4 by maintainers)

Top GitHub Comments

8reactions

TylerLeonhardtcommented, Aug 15, 2019

I’ve managed to drop about 50mbs off the package using a custom assembly load event (load xplat dlls from one location rather than 3) and deleting dev dependencies that shouldn’t ship with the product.

I think we can do even better with this approach while we wait for a better way offered by PSGet/Gallery

7reactions

TylerLeonhardtcommented, Aug 16, 2019

At the end of the day, PowerShellGet and the PowerShell Gallery are the customers. The scenarios should start there and work their way back to PowerShell. This probably does require a change in PowerShell, but what’s needed should ultimately come from a PowerShellGet perspective.