Rikki Tooley

I think I'm getting the same problem, with Yarn 3 and PnP. My scenario is I have a NextJS app and a component library built with `react-i18next` and packaged separately...

I shouldn't have written that context in the message, it's distracting. The error came from the workaround. @adrai can you comment on the workflow where second package uses react-i18next? How...

It's the exact same as the original post, except that `Layout` is in a separate package, and using Yarn with PnP to install the package.

So I went ahead and forked the project, changed `i18next` and `react-i18next` to be peer dependencies, and published it: [@rikkilt/next-i18next](https://www.npmjs.com/package/@rikkilt/next-i18next) `react-l18next` 's `I18NextProvider` is now initialised as expected and the...

The only downside I can see is that people will have to install `react-i18next` and `i18next` separately: ``` yarn add next-i18next react-i18next i18next ``` Otherwise there should be no functional...

@adrai I've deployed my app with my forked package to Vercel ("production mode"), and it's working as expected. So I've sent a PR. 👍 I think the problem in the...

Reading #136, I see this comment from @isaachinman > However, for advanced use cases, I believe that users may still need to use i18next > > What cases? If there...

Can you post the stack trace of the exception?

This looks like it could be related to #76. What version of the package are you using, and can you provide some more details on the project? Is it possible...

Sorry @rickerk6gdo, you can email your source to hello [at] rikk [dot] it but I can't promise I'll be able to try anything soon. In the spirit of open source,...