Bernd

I have the same problem. tsc and webpack are correctly finding the imports, but as soon as I want to run the code the require (in the genereated bundle.js) fails...

Did anyone of the maintainers already checkout this PR? I would be very interested in your feedback :)

@aralroca Was there any particular reason why you closed this PR?

@aralroca Is there any interest in this PR/Feature?

I just encountered the same issue after upgrading from 1.0.5 to 1.0.7-canary.1.

Digging through the commits since 1.0.5, I was able to pin-point the issue down to https://github.com/vinissimus/next-translate/blob/8abc45855cdc95bed873657379499c758483829a/src/useTranslation.tsx#L11 `useMemo()` has the wrong dependencies. `ctx.t` should be listed in the deps instead of...

Yes, I changed the code locally and verified that this causes the issue with `isFallback=true`. Why is `ctx.t` different on each render? `ctx` is a React context and the reference...

I was too hasty with my assumption. It seems this issue exists also before version 1.0.5. Something is broken when Next.js generates this fallback page (during the initial build). Inspecting...

I think I found the underlying issue: See https://nextjs.org/docs/basic-features/data-fetching#fallback-pages > - The page’s props will be empty. Even though next-translate loads the needed translations within the webpack loader and puts...

Is there any working/recommended solution for this issue?