Skip to main content

Version Compatibility

This page records the compatibility expectations that are visible in the current repo and highlights where admins should validate compatibility directly during deployment and upgrade work.

What The Repo Currently Shows​

The current workspace indicates:

  • the monorepo targets Node ^16.13.0 at the root
  • several packages target Node ^16.0.0
  • the client and web-player use React 18 and GraphQL 16

This suggests that production tooling and build/runtime expectations are centered around the Node 16 generation.

Practical Compatibility Guidance​

For production use, validate compatibility across:

  • server build and host runtime
  • Docker image/runtime environment
  • player or kiosk runtime
  • browser environment used by operators
  • upgrade path from the currently deployed version

Upgrade Sequencing Concerns​

The safest assumption is:

  • upgrade the server/build in a controlled maintenance window
  • preserve the persistent data
  • validate that players, screens, preview, and integrations still behave as expected after upgrade

If the deployment includes specialized playback-side components or kiosk devices, confirm they remain compatible with the upgraded server before broad rollout.

Browser And Client Expectations​

The client and web-player are modern web applications and should be treated accordingly.

Use current browsers and validate older operator workstations if the site depends on long-lived hardware or locked-down environments.

Environment Constraints To Track​

Over time, this page should be updated when you learn more about:

  • minimum supported server runtime
  • minimum supported browser versions
  • player-side compatibility constraints
  • release-to-release migration expectations