Skip to content

Using <Trans /> with the components prop gives a warning #1819

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
XAOPT opened this issue Dec 6, 2024 · 6 comments
Closed

Using <Trans /> with the components prop gives a warning #1819

XAOPT opened this issue Dec 6, 2024 · 6 comments
Labels

Comments

@XAOPT
Copy link

XAOPT commented Dec 6, 2024

🐛 Bug Report

#1805 still reproduces with [email protected] and [email protected]

To Reproduce

https://stackblitz.com/edit/vitejs-vite-59g4bx?file=package.json

Your Environment

"i18next": "^24.0.5",
"react-i18next": "^15.1.3",
"react": "^19.0.0",
"react-dom": "^19.0.0",
@XAOPT XAOPT changed the title Using <Trans /> with the components prop gives an error Using <Trans /> with the components prop gives a warning Dec 6, 2024
@adrai
Copy link
Member

adrai commented Dec 6, 2024

@aiktb can you have a look at this and verify?

@adrai
Copy link
Member

adrai commented Dec 6, 2024

@ahmadfsalameh seems that also may influence it: #1813

@adrai
Copy link
Member

adrai commented Dec 6, 2024

@ahmadfsalameh seems that also may influence it: #1813

as soon as this gets reverted this warning is not shown anymore...
so @ahmadfsalameh @aiktb @XAOPT please discuss and check how you like to proceed

@ahmadfsalameh
Copy link
Contributor

#1820

@rothsandro
Copy link
Contributor

#1820 is merged and released, but I still get this warning in our tests (but not when running the app).

Copy link

stale bot commented Apr 26, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Apr 26, 2025
@stale stale bot closed this as completed May 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants