Comments (4)
Hello @lupus-magnus,
the advanced example has a shared PageLayout
component that is used on all pages and in turn renders a Navigation
. Can you have a look if this works for you?
Note that the part where message namespaces are computed in the advanced example is entirely optional and only relevant for performance-senstive apps.
from next-intl.
It depends a bit. The advanced example is really focused on only providing only the minimum of messages for every page and so for such a situation I would suggest do add getStaticProps
for every page which filters the messages – yes.
If that's less of a concern for you, you can also utilize App.getInitialProps
to fetch general messages and hand them over to the provider.
from next-intl.
Hey! Thank you for answering it
In the mentioned example, there are two pages and you use GetStaticProps in both of them, to access the PageLayout messages.
If I have -let's say- 20 pages, the right thing to do would be to manually add that GetStaticProps in all of them for displaying my translated navbar?
from next-intl.
I hope your question was answered! Closing due to inactivity …
from next-intl.
Related Issues (20)
- Issue with multiple middleware chain HOT 1
- ESLint plugin HOT 2
- Handling Unsupported Languages HOT 1
- Support `localePrefix` setting per domain
- Support Intl.RelativeTimeFormat for `relativeTime` formatting HOT 3
- Docs Invisible Text on Search HOT 1
- Package path ./server.js is not exported from package HOT 2
- Error using `as={Link}` prop with when using `createSharedPathnamesNavigation` HOT 1
- Accidentally changed the locale after navigating when setting "localePrefix" to "never" HOT 2
- I cannot understand how to merge next-intl middleware with nextjs/platform HOT 3
- unhandledRejection: Error: NEXT_NOT_FOUND on terminal after running npm run dev HOT 7
- Official app router example: TypeError: Cannot read properties of undefined (reading 'en') HOT 1
- Error in 13.14.0: Expected a suspended thenable HOT 5
- [Docs]: Middleware matcher with Next-Auth HOT 1
- With i18n routing doesn't work with Next Canary (React 19) HOT 12
- Error: The React APIs of next-intl are currently not available in Server Components. HOT 2
- Route /en/xxx with `dynamic = "error"` couldn't be rendered statically because it used `headers` HOT 2
- Lazy-load intl-messageformat HOT 3
- Error: Insufficient params provided for localized pathname. HOT 1
- Link doesn't allow on production env HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from next-intl.