Add support for React 19

[cacabo]

Environment

• Package version(s): "@blueprintjs/core": "^5.11.0"
• Browser and OS versions: n/a

Feature request

I want to leverage React 19 in my app which uses Blueprint in order to benefit from the React compiler, other performance improvements, and the new hooks.

Blueprint currently requires:

npm error peer react@"^16.8 || 17 || 18" from @blueprintjs/[email protected]

I can use the beta compiler runtime until Blueprint can upgrade:

// package.json
{
    // ...
    "dependencies": {
        "react": "^18.3.1",
        "react-compiler-runtime": "^19.0.0-beta-63b359f-20241101",
        // ...
    }
}

Examples

[bofa]

I would love react 19 support to be able to leverage the improved custom elements integration.

[smeng9]

Currently there are still a lot of use cases of ReactDOM.render in the codebase which react 19 dropped support of. All of these need to be migrated to use createRoot

[bradchristensen]

Currently there are still a lot of use cases of ReactDOM.render in the codebase which react 19 dropped support of. All of these need to be migrated to use createRoot

I just had a quick scan through the repository and it looks like all the references to ReactDOM.render are either in tests/documentation, or they can be replaced on your app side if you provide a domRenderer prop to the relevant component. So I don't think this is a blocker, but it would be nice if Blueprint could either update to use the updated createRoot method by default, or provide an automatic backwards-compatible implementation.

[bppdddqqqq]

@bradchristensen I don't think so, see #7139

[bradchristensen]

@bradchristensen I don't think so, see #7139

Oh of course - I hadn't considered dependencies, sorry. Good catch!

[bppdddqqqq]

@bradchristensen I don't think so, see #7139

Oh of course - I hadn't considered dependencies, sorry. Good catch!

Unfortunately. I have tested other parts of Blueprint and it seems the most acted-up library is the aforementioned React-Popper. Others maintain functionality as is on React 18 and lower. What I fear is that this refactor would require either keeping the old Popper.js code and creating a switch whether it's React 17 and higher or React 16 (@floating-ui/react that supports React 19 does not support React 16 per this PR floating-ui/floating-ui#3103 ), or dropping React 16 support entirely in favor of Floating-UI.

Worst case scenario is to find a more supported solution or start cooking Popper.js wrapper that supports all flavors of React

[bppdddqqqq]

2 weeks and no news, guess I will take a look at it myself