8000 feat: support zstd by SevereCloud · Pull Request #389 · ai/size-limit · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

feat: support zstd #389

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.

Sign up for GitHub

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

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

feat: support zstd #389

wants to merge 1 commit into from

Conversation

SevereCloud
Copy link

Add support zstd

@ai
Copy link
Owner
ai commented Apr 28, 2025

I found that zstd is worse than brotli and the main reason to use it for dynamic HTML.

So you have any reason to use zstd?

@SevereCloud
Copy link
Author

So you have any reason to use zstd?

Compression / decompression speed

One way or another, size-limit should help in determining the usefulness of zstd

@ai
Copy link
Owner
ai commented Apr 29, 2025

Compression / decompression speed

But what is the reason to use zstd for static assets (like JS bundle file which we often test in Size Limit)?

@SevereCloud
Copy link
Author

But what is the reason to use zstd for static assets (like JS bundle file which we often test in Size Limit)?

The problem is that I can actually do this. Measuring the size using size-limit can help determine the usefulness of zstd

@ai
Copy link
Owner
ai commented Apr 29, 2025

Measuring the size using size-limit can help determine the usefulness of zstd

Releasing and support a feature is a lot of work for benchmark. It is better for you to do it with a fork and then report the usefulness :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@SevereCloud @ai
0