When using domain-based routing, use defaultLocale of a domain instead of the top-level one in case no other locale matches better on the domain (#1000) (42988b7), closes #998
Internationalization (i18n) is an essential part of the user experience, therefore next-intl gives you all the parts you need to get language nuances right.
🌟 ICU message syntax: Localize your messages with interpolation, cardinal & ordinal plurals, enum-based label selection and rich text.
📅 Dates, times & numbers: Apply appropriate formatting without worrying about server/client differences like time zones.
✅ Type-safe: Speed up development with autocompletion for message keys and catch typos early with compile-time checks.
💡 Hooks-based API: Learn a single API that can be used across your code base to turn translations into plain strings or rich text.
🚀 Next.js-native and performance-obsessed: App Router, Server Components, static rendering—pick the right tool for the right job, next-intl works everywhere.
⚔️ Internationalized routing: Provide unique pathnames per language and optionally localize pathnames for search engine optimization.
A minimal, but complete solution for internationalization in Next.js apps.
The npm package next-intl receives a total of 201,114 weekly downloads. As such, next-intl popularity was classified as popular.
We found that next-intl demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago.It has 1 open source maintainer collaborating on the project.
Last updated on 17 Apr 2024
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
A new report explores how advancements in LLMs are enhancing cyber threats, including polymorphic malware, personalized spearphishing, and the risk of hijacking customer service bots.
ESLint has approved an RFC that adds support for TypeScript configuration files, which is aimed at improving the developer experience and recognizing changes in the evolving JavaScript ecosystem.
The NVD is facing a significant backlog with over 12,500 CVEs awaiting analysis, and more than 50% of known exploited vulnerabilities (KEVs) left unenriched since mid-February.