VisActor / VisActor/VTable

What about react 19.1 support?

Open
#3,730 4 comments 8 reactions 1 assignee View on GitHub

@Rui-Sun is already working on this.

Since Apr 14, 2025.

Dominant language
TypeScript
Stars
3.7k
Forks
486
Avg merge
1d 19h
Merged PRs (30d)
16

Description

After updating to React 19, I get the following error: "Cannot read properties of undefined (reading 'ReactCurrentOwner')."

The thing is, starting with React 19, reactSharedInternals has been made more internal and less accessible.
As a temporary workaround to maintain compatibility, you can use the following hacks:
var ReactCurrentDispatcher = React.REACT_DEVTOOLS_GLOBAL_HOOK?._reactSharedInternals?.ReactCurrentDispatcher;
var ReactCurrentOwner = React.REACT_DEVTOOLS_GLOBAL_HOOK?._reactSharedInternals?.ReactCurrentOwner;
var ReactDebugCurrentFrame = React.REACT_DEVTOOLS_GLOBAL_HOOK?._reactSharedInternals?.ReactDebugCurrentFrame;
var ReactCurrentBatchConfig = React.REACT_DEVTOOLS_GLOBAL_HOOK?._reactSharedInternals?.ReactCurrentBatchConfig;
var ReactCurrentActQueue = React.REACT_DEVTOOLS_GLOBAL_HOOK?._reactSharedInternals?.ReactCurrentActQueue;

Please add support for React 19.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.