React 19

[AmirhoseinHesami]

will you support react 19?

[meowsus]

I'm curious about this as well. Next.js v15 came out last month and they are depending on a supposedly stable RC version of React & React Dom v19. I'm trying to upgrade my project to their new version and am being blocked by the following conflict:

Could not resolve dependency:
peer react-dom@"^16.8.5 || ^17.0.0 || ^18.0.0" from @hello-pangea/[email protected]
node_modules/@hello-pangea/dnd
  @hello-pangea/dnd@"^16.6.0" from the root project

Conflicting peer dependency: [email protected]
node_modules/react-dom
  peer react-dom@"^16.8.5 || ^17.0.0 || ^18.0.0" from @hello-pangea/[email protected]
  node_modules/@hello-pangea/dnd
    @hello-pangea/dnd@"^16.6.0" from the root project

I pulled down the code and did a quick upgrade from React v18 to v19. Everything seems to be working in Storybook as expected. I ran the jest tests and received one failure that seemed dependency related and simple to fix (ReferenceError: MessageChannel is not defined coming from react-dom/server). I couldn't run the browser tests because they're in cypress.

As far as peer dependencies, there seem to be 7 that would require upgrading:

 WARN  Issues with peer dependencies found
.
├─┬ @atlaskit/css-reset 6.10.1
│ ├── ✕ unmet peer react@"^16.8.0 || ^17.0.0 || ^18.0.0": found 19.0.0-rc-66855b96-20241106
│ └─┬ @atlaskit/theme 13.0.0
│   ├── ✕ unmet peer react@"^16.8.0 || ^17.0.0 || ^18.0.0": found 19.0.0-rc-66855b96-20241106
│   ├─┬ @atlaskit/ds-lib 2.5.0
│   │ ├── ✕ unmet peer react@"^16.8.0 || ^17.0.0 || ^18.0.0": found 19.0.0-rc-66855b96-20241106
│   │ └─┬ react-uid 2.3.3
│   │   └── ✕ unmet peer react@"^16.8.0 || ^17.0.0 || ^18.0.0": found 19.0.0-rc-66855b96-20241106
│   └─┬ @atlaskit/tokens 1.59.1
│     └── ✕ unmet peer react@"^16.8.0 || ^17.0.0 || ^18.0.0": found 19.0.0-rc-66855b96-20241106
├─┬ @storybook/react 8.3.0
│ └─┬ react-element-to-jsx-string 15.0.0
│   ├── ✕ unmet peer react@"^0.14.8 || ^15.0.1 || ^16.0.0 || ^17.0.1 || ^18.0.0": found 19.0.0-rc-66855b96-20241106
│   └── ✕ unmet peer react-dom@"^0.14.8 || ^15.0.1 || ^16.0.0 || ^17.0.1 || ^18.0.0": found 19.0.0-rc-66855b96-20241106
├─┬ @testing-library/react 14.3.1
│ ├── ✕ unmet peer react@^18.0.0: found 19.0.0-rc-66855b96-20241106
│ └── ✕ unmet peer react-dom@^18.0.0: found 19.0.0-rc-66855b96-20241106
├─┬ react-virtualized 9.22.5
│ ├── ✕ unmet peer react@"^15.3.0 || ^16.0.0-alpha || ^17.0.0 || ^18.0.0": found 19.0.0-rc-66855b96-20241106
│ └── ✕ unmet peer react-dom@"^15.3.0 || ^16.0.0-alpha || ^17.0.0 || ^18.0.0": found 19.0.0-rc-66855b96-20241106
├─┬ react-window 1.8.10
│ ├── ✕ unmet peer react@"^15.0.0 || ^16.0.0 || ^17.0.0 || ^18.0.0": found 19.0.0-rc-66855b96-20241106
│ └── ✕ unmet peer react-dom@"^15.0.0 || ^16.0.0 || ^17.0.0 || ^18.0.0": found 19.0.0-rc-66855b96-20241106
├─┬ react-redux 9.1.2
│ ├── ✕ unmet peer react@^18.0: found 19.0.0-rc-66855b96-20241106
│ └─┬ use-sync-external-store 1.2.0
│   └── ✕ unmet peer react@"^16.8.0 || ^17.0.0 || ^18.0.0": found 19.0.0-rc-66855b96-20241106
└─┬ use-memo-one 1.1.3
  └── ✕ unmet peer react@"^16.8.0 || ^17.0.0 || ^18.0.0": found 19.0.0-rc-66855b96-20241106

So an upgrade definitely seems doable with relatively minimal effort, provided that each peer also supports React 19.