Team,
We attempted to adopt Bynder Compact View v5 to unblock our asset selector and align with our React 19 upgrade. The NPM/Yarn packages appear broken (
) or incompatible with React 19 (
), and even the official demo and the script served from Bynder’s CDN produce failure. Specifically, the UI displays an “empty” label in the select box next to the “Add asset” button, and the “Add asset” button itself is not clickable.
We were unable to locate links to previous v5 releases to roll back to a known-good build. This leaves us without a viable integration path and is currently blocking our upgrade plan.
What we tried
- Verified behavior against Bynder’s official demo and the script provided on their site (https://ucv.bynder.com/5.0.5/modules/compactview/bynder-compactview-5-latest.js).
- Observed consistent UI failure: the selector shows “empty,” and the “Add asset” action cannot be triggered.
- Searched for prior versions or pinned builds of v5 (no obvious way to access earlier point releases).
- Tried to use npm package v3-v4
Impact
- Our application upgrade is blocked until we have a working Bynder Compact View integration that functions with React 19, or a stable fallback we can pin to.
- Delivery timelines are at risk because we cannot proceed with the asset selection flow in environments that depend on v5.
- Without access to previous, working v5 builds, we lack a short-term rollback option, increasing the likelihood of continued delays.
What we need from the vendor
- A working, React 19–compatible package for Bynder Compact View v5 published to NPM/Yarn, or
- A stable, compiled CDN build for a known-good v5 release, with accessible versioned links so we can pin reliably, and
- Clarity on a release plan and timeline for resolving the current breakage, plus a brief changelog so we can assess risk.
Why this matters now We are at the point where this integration is a critical path dependency. The absence of a functioning package and the lack of accessible, versioned prior builds leave us with no immediate workaround. We need a concrete path forward (either a fixed current version or a reliable previous version we can pin) to keep our upgrade on track and avoid further delays.
Please refer to this issue: https://nextjs.org/blog/CVE-2025-66478
