v0.2.3

This is the fourth release in the 0.2.x series of http4s-dom and is binary- and source-compatible with every previous 0.2.x release. It is published against the http4s 0.23.x series with Scala 2.12, 2.13, and 3.1+ and Scala.js 1.8+.

This release fixes a bug in the FetchClient. Notably, this is the second bug identified by the Node.js fetch implementation, which follows the WHATWG specification more closely than browser implementations.

What's Changed

• Chunked requests should be made strict by @armanbilge in #154

Full Changelog: v0.2.2...v0.2.3

v1.0.0-M33

This release brings you everything in v0.2.2 but is built against http4s v1.0.0-M33. It is not binary-compatible with any previous release.

v0.2.2

This is the third release in the 0.2.x series of http4s-dom and is binary- and source-compatible with v0.2.0 and v0.2.1. It is published against the http4s 0.23.x series with Scala 2.12, 2.13, and 3.1+ and Scala.js 1.8+.

This release is prompted by a critical optimization to the MimeDB in http4s-core that was released in http4s v0.23.12. The size of JS artifacts should now be substantially smaller, which improves performance and resolves several usability issues (#30, #33, #46, #119).

In other news, http4s-dom now also supports Node.js v18+ which added experimental support for fetch!

User-facing PRs

• Update to http4s 0.23.12 by @armanbilge in #147
• Add support for Node.js 18 by @armanbilge in #148

Full Changelog: v0.2.1...v0.2.2

v1.0.0-M32

This release brings you everything in v0.2.1 but is built against http4s v1.0.0-M32. It is not binary-compatible with any previous release.

v0.2.1

This is the second release in the 0.2.x series of http4s-dom and is binary- and source-compatible with v0.2.0. It is published against the http4s 0.23.x series with Scala 2.12, 2.13, and 3.1+ and Scala.js 1.8+.

This release features a WebSocketClient that implements the WSClient interface introduced in http4s v0.23.11. Try it out with the interactive example in the docs!

Note that the WSClient interface is also implemented by the http4s-jdk-http-client. For example, if you implement a GraphQL client with WSClient you can cross-compile it and deploy to both the browser and the JVM!

User-facing PRs

• Implement WebSocket client by @armanbilge in #93
• WebSocket client docs/example by @armanbilge in #94

Full Changelog: v0.2.0...v0.2.1

v1.0.0-M31

This release brings you everything in v0.2.0 but is built against http4s v1.0.0-M31. It is not binary-compatible with any previous release. It also drops support for Scala 2.12 due to support being dropped upstream in http4s itself.

Thanks to the ongoing entity re-design effort in http4s-core, it was possible to apply some optimizations to http4s-dom in #99.

v1.0.0-M30

This release brings you everything in v0.2.0 but is built against http4s v1.0.0-M30. It is not binary-compatible with any previous release.

v1.0.0-M29

This release brings you everything in v0.2.0 but is built against http4s v1.0.0-M29. It is not binary-compatible with any previous release.

v0.2.0

This is the first release in the v0.2.x series of http4s-dom. It is compatible with http4s 0.23.x series and published for Scala 2.12, 2.13, and 3.1+ with Scala.js 1.7+. This release is binary-incompatible with the v0.1.x series due to a breaking update of the scala-js-dom dependency to v2.0.0.

Although there are no new features or bug fixes since v0.1.0, we are excited about:

• Brand new docs with a live example (!) at https://http4s.github.io/http4s-dom/
• Our first published artifact for Scala 3 🎉

User-facing PRs

• Establish series/0.2 against sjs-dom 2.x by @armanbilge in #28
• Create docs by @armanbilge in #29

Full Changelog: v0.1.0...v0.2.0

v0.1.0

This is the first stable release of the new http4s-dom which brings http4s to the browser! It is compatible with http4s 0.23.x series and published for Scala 2.12 and 2.13 with Scala.js 1.x.

This project was initially incubated in the main http4s repository as part of http4s/http4s#4938.

Features

• FetchClient by @rpiaggio in http4s/http4s#5101
• ServiceWorker integration by @armanbilge in http4s/http4s#5089