{"repo":"amannn/next-intl","free":true,"listed":false,"github":"https://github.com/amannn/next-intl","clone":"git clone https://github.com/amannn/next-intl.git","description":"🌐 Internationalization (i18n) for Next.js","language":"TypeScript","stars":4348,"topics":["react","next","i18n","date-formatting"],"license":"MIT","category":"ui-components","readme_excerpt":"Internationalization for Next.js. Features 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. What does it look like? → Read the docs Hosted on Vercel","default_branch":null,"files":null,"tree":[],"storefront":"/r/amannn","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/amannn/next-intl/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}