We're hitting this on Grafana Cloud too (stack on v13.1.0). Sharing the confirmed
root cause + a concrete ask, since the Grafana 13 rollout breaks this for every
Cloud user of the plugin:
Root cause: Grafana 13 ships React 19. The catalog's latest published
version is 0.4.5 (April 2024) — a React 18 build that references the React
internal ReactCurrentOwner, which React 19 removed. So module.js throws on load:
Error: Could not load plugin: quickwit-quickwit-datasource
Caused by: Cannot read properties of undefined (reading 'ReactCurrentOwner')
Grafana Cloud auto-upgraded core to 13.x, so the plugin frontend now fails for all
Cloud users — config page, query editor, and every dashboard panel on the datasource.
The fix already exists here: v0.6.0 ("React 19 compatibility for Grafana 13",
PR #170 externalizes react/jsx-runtime). I verified the 0.6.0 bundle externalizes
the JSX runtime. The only problem is 0.6.0 was never published to the Grafana
catalog — the catalog still serves 0.4.5, and managed Grafana Cloud can only
install catalog versions.
Ask: could a maintainer publish 0.6.0 (ideally 0.5.x too) to the catalog?
On grafana.com → your org → My Plugins → submit the new version. That one action
unblocks every affected Cloud user with zero changes on our end. Happy to help with
the submission or open a PR if anything's needed — this is a production outage for us.
We're hitting this on Grafana Cloud too (stack on v13.1.0). Sharing the confirmed
root cause + a concrete ask, since the Grafana 13 rollout breaks this for every
Cloud user of the plugin:
Root cause: Grafana 13 ships React 19. The catalog's latest published
version is 0.4.5 (April 2024) — a React 18 build that references the React
internal
ReactCurrentOwner, which React 19 removed. Somodule.jsthrows on load:Grafana Cloud auto-upgraded core to 13.x, so the plugin frontend now fails for all
Cloud users — config page, query editor, and every dashboard panel on the datasource.
The fix already exists here:
v0.6.0("React 19 compatibility for Grafana 13",PR #170 externalizes
react/jsx-runtime). I verified the 0.6.0 bundle externalizesthe JSX runtime. The only problem is 0.6.0 was never published to the Grafana
catalog — the catalog still serves 0.4.5, and managed Grafana Cloud can only
install catalog versions.
Ask: could a maintainer publish 0.6.0 (ideally 0.5.x too) to the catalog?
On grafana.com → your org → My Plugins → submit the new version. That one action
unblocks every affected Cloud user with zero changes on our end. Happy to help with
the submission or open a PR if anything's needed — this is a production outage for us.