Using i18nextEager pipe now triggers runtime error

[wjbux]

Hi Sergey, thank you for taking the time to look at this.

After upgrading to Angular 20 and using the i18nextEager pipe, I consistently get NG203 errors (below).

I believe this is because now the pipe is a standalone component, it is attempting to call takeUntilDestroyed() outside an injection context, which requires a DestroyRef to be passed to it. Could be wrong but I believe this is the issue.

Any help appreciated!

EDIT - I believe this happens here

[Romanchuk]

@wjbux Sorry for not answering for half a year.

Try out this version: 21.0.1-0