Git Product home page Git Product logo

Comments (3)

amannn avatar amannn commented on August 30, 2024 1

Hey, thank you for the question! The section Changes to NextIntlClientProvider in the changelog for 3.0 is relevant to you:

(...) Using NextIntlClientProvider with the App Router

If you're using NextIntlClientProvider with the App Router, there has been a slight change to the semantics. If you're rendering NextIntlClientProvider within a Server Component, the component will pass defaults for locale, now and timeZone to the client side.

If you're already providing these options, then you're set.

If you're not, be aware that this will by default opt the corresponding page into dynamic rendering. If your app relies on static rendering, you can avoid this by passing all of the mentioned options, or by enabling static rendering explicitly (see the previous section).

Adapting the call to NextIntlClientProvider in your layout fixes this for me:

<NextIntlClientProvider
  timeZone="Europe/Vienna"
  now={new Date()}
  locale={locale}
  messages={messages}
>
  {children}
</NextIntlClientProvider>

Hope this helps!

from next-intl.

amannn avatar amannn commented on August 30, 2024 1

You're calling createSharedPathnamesNavigation within a component, this causes a new Link component to be created on each render, causing the infinite loop.

You can fix this by moving the call outside of your component.

from next-intl.

el-j avatar el-j commented on August 30, 2024

@amannn thank u very much. that was fast and indeed that helped! But now it is even more problematic as the Link component creates a renderloop after static export...

i have prepared the sandbox to show the issue. useing the next-intl-Link component and the standard NextJs-Link component.

please open the sandbox link in bottom.
image

in the preview start:3000 there is the running static export. hover over the next-intl Link (go to sub).
you will see the render loop in the console as u can see from the screenshot. as well as the Link does not do anything onClick. Same issue in the subpage for the go back.

any idea why this happens? do you need a new issue for this?
(nextjs 14.0.4, next-intl: 3.4.0)

codesandbox

from next-intl.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.