TypeError: Cannot read properties of null (reading 'useContext')

[leeoniya]

Describe the bug

I created a react-data-grid-builds repo to test the latest commits here before you officially publish the next beta.

I simply run npm run build, then npm pack and commit the contents of the archive to the repo. I then use it like "react-data-grid": "leeoniya/react-data-grid-builds#c589d2c7a0794e66536b2edaf61174d6d5a22513",

I tried to upgrade react-data-grid this way in my grafana PR/branch and got the error below, which i do not see with latest published beta.

To Reproduce

Expected behavior

no crash

Link to Minimal Reproducible Example

Environment

• react-data-grid version: 720a253
• react/react-dom version: 18.3.1

Additional context

[leeoniya]

oh, does the new version require react v19?

react-data-grid/package.json

Lines 99 to 102 in 720a253

	"peerDependencies": {
	"react": "^19.0",
	"react-dom": "^19.0"
	}

[amanmahajan7]

Correct. We dropped support for React 19 in beta 48

[leeoniya]

thanks for confirming.

i realize that this is an OSS project (i maintain several besides working at Grafana) and no one is owed anything, but i will point out that most of the world still runs React 18. dropping support for it after 47 "beta" releases, less than two months after 19.0 was released does feel like a bit of a rug-pull for us after we put significant effort and trust into the API remaining mostly stable until RC/release.

as a solo maintainer, i totally get it. but as someone who makes bets on great dependencies for Grafana, this one is stinging quite a bit. we'll work through it in time, but figured i'd give my $0.02. nevertheless, thanks for your continued effort here :)

[nstepien]

less than two months after 19.0 was released

https://react.dev/versions

https://github.com/facebook/react/releases

• 19.1.0 was released on March 28, 2025
• 19.0.0 was released on December 5, 2024
• 19.0.0 rc was released in April 2024, over a year ago
• react-data-grid added dual support for React 18 and React 19 since July 15, 2024: Add support for React 19 #3545

Was that not enough time to migrate to React 19?

[leeoniya]

Was that not enough time to migrate to React 19?

unfortunately, this is rather complicated. Grafana is a platform, with a large/diverse plugin ecosystem. we cannot just migrate Grafana itself without also making sure hundreds of external plugins work with React 19. while we could transition Grafana's own use of React, that would mean likely breaking third party plugins [and dashboards which use them] for thousands of users. this ecosystem compat is the reason we had to deprecate but still co-run AngularJS (yes, the original) alongside React for multiple years before finally removing it in Grafana 12 earlier this month.

additionally, most large projects dont upgrade to an RC or .0 release, but wait for a few patch releases to make sure any 0-day bugs are ironed out. i'm not aware of any major React libs that are 19-exclusive today; this was a complete surprise. i can understand this once 19.x has maybe 70% of the users, but the current 18.x install base outnumbers 19.x something like 7:1 or even greater.

the other bit is, there's no strong reason to migrate from 18 to 19 if you dont need the new bells/whistles. don't get me wrong, we're still going to do it of course, but putting in the effort to move an entire ecosystem from 18 to 19 when nothing is broken, with 19.x still just a few months old and far less used than 18 is a really untenable expectation, imo.