-
Notifications
You must be signed in to change notification settings - Fork 29.2k
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
Support for zstd #48412
Comments
There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment. For more information on how the project manages feature requests, please consult the feature request management document. |
I think this is still relevant as the 22 👍 reactions (and counting) shows. |
Zstd Content-Encoding will start shipping 🚢 soon in modern web browsers, and its support in Node could be very handy, imo 🙄 |
available in in Chrome 121 now. |
Support is also being tracked on caniuse: https://caniuse.com/zstd |
Fixes: nodejs#48412 PR-URL: nodejs#52100
Fixes: nodejs#48412 PR-URL: nodejs#52100
Fixes: nodejs#48412 PR-URL: nodejs#52100
Fixes: nodejs#48412 PR-URL: nodejs#52100
Fixes: nodejs#48412 PR-URL: nodejs#52100
Fixes: nodejs#48412 PR-URL: nodejs#52100
Fixes: nodejs#48412 PR-URL: nodejs#52100
Fixes: nodejs#48412 PR-URL: nodejs#52100
Potential PR for basic support (no custom dictionaries): #52100 |
Fixes: nodejs#48412 PR-URL: nodejs#52100
Fixes: nodejs#48412 PR-URL: nodejs#52100
Fixes: nodejs#48412 PR-URL: nodejs#52100
Fixes: nodejs#48412 PR-URL: nodejs#52100
Fixes: nodejs#48412 PR-URL: nodejs#52100
What is the problem this feature will solve?
zstd and the
application/zstd
media type were standardized in 2018 in RFC8478 (and refined in RFC8878). In the context of the web, support is becoming more widespread:Browsers
Web servers
Tools
What is the feature you are proposing to solve the problem?
Add support for zstd compression in Node's zlib module.
What alternatives have you considered?
No response
The text was updated successfully, but these errors were encountered: