You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Unable to install react-helmet-async in React 19 #238
This library covers more than what React 19 offers currently: #239 (comment)
Reacted by Meryovi De Dios, Agostino Carandente, Kai Dorschner, mkrause, Kirill Anikin, AbdelrahmanTorki, Bo_Ryong, Thomas Wang, iron-cherep, Reagan Odhiambo and 6 more
I installed react-helmet with npm install react-helmet-async --legacy-peer-deps
Is there a way to test my metadata on localhost?
cause i don't see on any component any of my metadata.
Is the legacy-peer-deps the correct way?
thanks!
Activity
DanielSchiavini commentedon Dec 20, 2024
We might not need it anymore: https://react.dev/blog/2024/12/05/react-19#support-for-metadata-tags
slorber commentedon Dec 30, 2024
This library covers more than what React 19 offers currently: #239 (comment)
imkss commentedon Apr 10, 2025
Do we really need react-helmet-async in react 19?
https://egghead.io/hoist-title-and-meta-tags-in-react-19~h6z5l
slorber commentedon Apr 10, 2025
Again, yes, React 19 features do not cover everything
#239 (comment)
mbdev3 commentedon Apr 15, 2025
For those getting a warning or don't want to everytime run an npm i --force add this to package.json:
"overrides": { "react-helmet-async": { "react": "^19.0.0", "react-dom": "^19.0.0" } }swapnilahmedshishir commentedon Apr 17, 2025
Option 1: Use --legacy-peer-deps (recommended for now)
This tells npm to install it anyway and ignore the peer conflict:
npm install react-helmet-async --legacy-peer-deps✅ Works in most cases if the package still functions fine under React 19 (which it probably does unless there are breaking changes).
Option 2: Use --force (riskier)
npm install react-helmet-async --forceThis forces npm to install it no matter what. But be careful — this can break stuff if the library really isn't compatible.
AchmetCh commentedon Jun 4, 2025
I installed react-helmet with npm install react-helmet-async --legacy-peer-deps
Is there a way to test my metadata on localhost?
cause i don't see on any component any of my metadata.
Is the legacy-peer-deps the correct way?
thanks!
Rupon100 commentedon Aug 31, 2025
but peer dependency warnings will show in the console
fix: add `--legacy-peer-deps` to npm install
staylor commentedon Mar 6, 2026
#260