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
I'm using next-i18next in a project with 7 namespaces. In upgrading that from 15.0.0 to 15.2.0 I started to see Type instantiation is excessively deep and possibly infinite with my useTranslation call.
I have narrowed this down to the underlying i18next dependency bumping from 23.7.13 -> 23.7.14. The issue persists with a bump to latest 23.10.0.
Last working version
Worked up to version: 23.7.13
Stopped working in version: 23.7.14
To Reproduce
I've tried to create a reproduction of this but have been unable to so far - but will keep trying to narrow down the issue. Sorry, I appreciate this isn't very helpful right now.
Expected behaviour
Type definitions to work as before.
Your Environment
runtime version: Node 20 LTS
i18next version: See above
os: Mac
any other relevant information
I saw from the release notes that the release was intended to fix types for array access. Are there any examples translation json structures that would be parsed differently before / after this release?
The text was updated successfully, but these errors were encountered:
Just as a heads-up: I'm currently sick and will likely not be able to look into this myself for at least a couple weeks; but as both of you correctly pointed out already anyway: without a minimal reproducible example, this is probably next to impossible to debug, anyway... :(
馃挜 Regression Report
I'm using
next-i18next
in a project with 7 namespaces. In upgrading that from 15.0.0 to 15.2.0 I started to seeType instantiation is excessively deep and possibly infinite
with myuseTranslation
call.I have narrowed this down to the underlying
i18next
dependency bumping from 23.7.13 -> 23.7.14. The issue persists with a bump to latest 23.10.0.Last working version
Worked up to version: 23.7.13
Stopped working in version: 23.7.14
To Reproduce
I've tried to create a reproduction of this but have been unable to so far - but will keep trying to narrow down the issue. Sorry, I appreciate this isn't very helpful right now.
Expected behaviour
Type definitions to work as before.
Your Environment
I saw from the release notes that the release was intended to
fix types for array access
. Are there any examples translation json structures that would be parsed differently before / after this release?The text was updated successfully, but these errors were encountered: