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

Feature: Package size #8114

Open
vanlooverenkoen opened this issue Oct 7, 2024 · 6 comments
Open

Feature: Package size #8114

vanlooverenkoen opened this issue Oct 7, 2024 · 6 comments

Comments

@vanlooverenkoen
Copy link

It would be nice to know what the actual size is of a package. And see this on pub.dev.

2 type of sizes would be interesting

  • Size excl dependencies
  • Size incl dependencies
@sigurdm
Copy link
Contributor

sigurdm commented Oct 7, 2024

I agree it would be nice to list the archive sizes on the "versions" page.

However remember that (given dart's treeshaking) the size affect on the actual produced app is largely unrelated to the size of the package.

Size incl dependencies

This is a lot harder to make useful - dependencies can often be shared. What would be the use case for this?

@vanlooverenkoen
Copy link
Author

Fair point. But at least you have an idea of the size of the package without actually digging into the code. Just an idea

@sigurdm
Copy link
Contributor

sigurdm commented Oct 7, 2024

Maybe just listing the number of transitive dependencies of a package (in the default resolution) somewhere would be useful...

@isoos
Copy link
Collaborator

isoos commented Oct 7, 2024

Maybe just listing the number of transitive dependencies of a package (in the default resolution) somewhere would be useful...

We have that in the scoring page, after the direct dependencies:
image

However, it changes over time (as the dependent packages may change) and it also depends on the SDK being used for the analysis.

@isoos
Copy link
Collaborator

isoos commented Oct 7, 2024

Also: what size are we interested in? gzipped archive size, uncompressed total size (incl/excluding tests and other assets)? It can vary based on the needs and uses of a package.
I think we should expose the single archive file size, and maybe the total archive file size, but other than that, the analysis gets into a grey area.

@sigurdm
Copy link
Contributor

sigurdm commented Oct 7, 2024

For the version listing I would be interested in the compressed archive size.

Maybe the others are useful for some purposes. But yeah - a very grey area.

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

No branches or pull requests

3 participants