@typescript-eslint errors in `i18n.ts` about next-intl

[amannn]

To address the two lines reported by your linter:

1. Narrowing with .includes is something that's unfortunately not supported in TypeScript (microsoft/TypeScript#36275). If you want to comply with that lint rule, you can use one of the proposed workarounds in that thread or similar ones.
2. The dynamic import can't really be typed in a meaningful way here, but if you like, you can add your own runtime validation on top. However, next-intl includes a lot of error-handling capabilities that help with catching errors in messages.

Generally, the code presented works fine without any issues. If you choose to enable lint rules that find theoretical issues in code, I'm afraid it's your job to find patterns that align with your rules.

Sorry for pushing a bit back here, but next-intl has to operate in the spectrum of integrating deeply with tools like React and Next.js, while also working well with TypeScript. The code that's reported by your linter here doesn't have any issues, therefore I'd question if you really want those rules or if you want to disable them here. next-intl tries to integrate with TypeScript in any way where actual issues can be discovered (e.g. a type-safe t function), but the snippet you've pasted above just isn't an issue.

I'm closing this issue therefore, I hope you can understand.