Skip to content

Releases: datocms/react-datocms

v8.0.6 — default video poster to thumbnailUrl

15 Jun 14:00

Choose a tag to compare

  • VideoPlayer: default poster to data.thumbnailUrl a65dccd

v8.0.5...v8.0.6

v8.0.5 — automatic sizes="auto"

12 Jun 10:08

Choose a tag to compare

Automatic sizes="auto" for lazy-loaded responsive images

When you don't pass an explicit sizes prop (and the image isn't priority), the image components now emit sizes="auto, 100vw" together with loading="lazy".

On supporting browsers (Chrome/Edge 126+, Opera, Samsung Internet, Firefox 150+) the browser picks the optimal srcset candidate from the image's real laid-out width instead of assuming the full viewport width (100vw) — often a much smaller download. Browsers without support (e.g. Safari) fall back to 100vw, i.e. the previous behavior, so there is no regression.

  • An explicit sizes (prop, or coming from the responsiveImage GraphQL query) still takes precedence — we never override it.
  • priority images are unchanged (they load eagerly, and sizes="auto" requires loading="lazy").
  • Applies to both the SSR/native components and the JavaScript lazy-loading components.

v8.0.3

14 May 12:08

Choose a tag to compare

  • Expose revealStega utility from @datocms/content-link c8ef52a
  • Rename SRCImage to RSCImage (with deprecated alias for back-compat) 5d12722

v8.0.2...v8.0.3

v8.0.1

23 Mar 11:50

Choose a tag to compare

  • Upgrade @datocms/content-link to 0.3.19 and expose hue prop b641d25

Full Changelog: v8.0.0...v8.0.1

v8.0.0

25 Feb 08:58

Choose a tag to compare

Breaking change: @mux/mux-player-react is now an optional peer dependency

Previously, react-datocms bundled @mux/mux-player-react as a direct dependency with a "*" version range. This caused issues where package managers could resolve to outdated versions of the Mux player, leading to subtitles/closed captions not loading on Chrome.

Starting with v8.0.0, @mux/mux-player-react is declared as an optional peer dependency.

How to upgrade

If you use <VideoPlayer />, add @mux/mux-player-react to your project's dependencies:

npm install @mux/mux-player-react

We recommend version 3.11.4 or later, which includes the Chrome subtitles fix.

If you don't use <VideoPlayer />, no action is needed — the Mux player package will no longer be pulled into your bundle at all.

Why this change?

  • Fixes subtitles not loading on Chrome (forum thread)
  • Gives you control over which Mux player version you use
  • Reduces bundle size for projects that don't use <VideoPlayer />

v7.2.10

26 Jan 08:09

Choose a tag to compare

  • Fix hoverOnly type compatibility with controller 753293c
  • Add hoverOnly option to ClickToEditOptions 6600000

v7.2.9...v7.2.10

v7.2.9

25 Jan 09:46

Choose a tag to compare

  • Allow enableClickToEdit prop to accept false value 998b67e

v7.2.8...v7.2.9

v7.2.7

23 Jan 14:44

Choose a tag to compare

  • Add content link support to VideoPlayer ca2b4fe
  • Update ContentLink documentation with stripStega details 8ada688
  • Update ContentLink documentation with stripStega details 2276cf7

v7.2.6...v7.2.7

v7.2.6

23 Jan 12:21

Choose a tag to compare

  • Update package-lock.json for @datocms/content-link 0.3.8 dc3fe8e
  • Update @datocms/content-link to 0.3.8 7af9b43
  • Update ContentLink documentation with stripStega prop 1e68372

v7.2.6-1...v7.2.6

v7.2.6-1

23 Jan 07:19

Choose a tag to compare

v7.2.6-1 Pre-release
Pre-release
  • Add stripStega prop to ContentLink component f13104a

v7.2.6-0...v7.2.6-1