Support for zstd

[JamieMagee]

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

• Chrome
  • Issue 1246971: Implement zstd content-encoding
  • Expected to land in 117
• Firefox
  • Bug 1301878: Implement support for Zstandard (zstd)
  • Still under discussion

Web servers

• Caddy
  • Available in v2
• Nginx
  • Available as a module

Tools

• cUrl
  • Available in 7.72.0
• wget2
  • Available in 1.99.2

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

[github-actions[bot]]

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.

[JamieMagee]

I think this is still relevant as the 22 👍 reactions (and counting) shows.

[bricss]

Zstd Content-Encoding will start shipping 🚢 soon in modern web browsers, and its support in Node could be very handy, imo 🙄

[yyfearth]

available in in Chrome 121 now. Accept-Encoding: gzip, deflate, br, zstd

[JamieMagee]

Support is also being tracked on caniuse: https://caniuse.com/zstd

[jkrems]

Potential PR for basic support (no custom dictionaries): https://github.com/nodejs/node/pull/52100

[github-actions[bot]]

There has been no activity on this feature request for 5 months. To help maintain relevant open issues, please add the https://github.com/nodejs/node/labels/never-stale label or close this issue if it should be closed. If not, the issue will be automatically 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.

[skhaz]

Keep