React v18 unsupported

[alexdhaynes]

Is there currently a roadmap for react v18 support?

[keslert]

#1878 #1971. Lots of interest in v18 support.

[carbon-frontend]

Any rough ETA possible for this change? Eagerly waiting for this update!

[ubRoman]

Please add support for React 18.

[DiegoGonzalezCruz]

hi! any ETA on react 18?

[orshih6]

hi i'm waiting. :)

[shekhardtu]

Hi @diegomura , Is there any rough estimate? We eagerly waiting for the react18 support

[crice88]

Would love support for React 18! Love the product and would hate to have to migrate off...

[ryandey]

Same, would definitely like to see React 18 support when possible

[jeetiss]

Can someone explain what is not working on 18 react or what kind of problems you have?

[ubRoman]

The react dependency is missing react 18+, so the installation and updates went painful with npm as we need to set the flag —legacy-peer-deps, otherwise npm will not let as do any updates at all. On every modul in the project.

[jeetiss]

is this should help then?

• Add support for React 18 #1879

[pierremouchan]

Any updates...?

I saw some workarounds on github and stack overflow but they all seems to not work completely.

[frindly]

To avoid having to add --legacy-peer-deps when running npm install, you can add an override to your package.json:

"dependencies": {
   ...
    "@react-pdf/renderer": "^3.0.1",
   ...
},
"overrides": {
    "@react-pdf/renderer": {
      "react": "latest"
    }
  }

[gitname]

In addition to the "overrides" property mentioned by @frindly above 🙌 , if you are using TypeScript and want to use some of the SVG-related components offered by @react-pdf/renderer, you may encounter compiler errors related to passing children to those components.

Here's a write-up about that problem and how I have worked around it. I got the workaround from this comment, written by GitHub user @antoineharel 🙌.

https://gist.github.com/gitname/bdc1fb7fe5bd0c22f6656b7905f57cd6#problem-2-inaccurate-typescript-types

[jeetiss]

duplicate of #1878