-
-
Notifications
You must be signed in to change notification settings - Fork 245
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
👋 Who is using next-intl? #138
Comments
Hello from Japan. Thanks for your work on this library. We use it at my company in our online paystub application. Soon we will use it for payroll and accounting products too. We want our products to work well for both native Japanese speakers and the growing immigrant population (like myself). By the way, I haven't been able to figure out how to specify a global currency type for formatNumber. It would be great if we could Update {
number: {
currency: {
style: "currency",
currency: "JPY",
},
},
} |
Hey @tacomanator, thanks for leaving a note here, I'm really glad to hear that Great you figured out a solution with the global formats, that looks correct to me! |
@amannn Hello from china. I want to know how to sync the |
Hi @3lang3 and thank you for your kind words! If you don't mind, I'd like to avoid answering usage questions in this thread. Your question is best redirected to Stack Overflow, I check in there occasionally to see if a user of |
Hey @amannn Hello from Hungary! I've found this package shortly after I migrated to Next's app folder structure, and saw they have removed the built in support for Other than that it's capable for fully replacing Good work 👍 |
Hey @amannn Hello from China! I've found this package to be extremely helpful since we're always a bilingual team at heart. I'm the Founder and CEO at Zolplay and I've recently revamped the site to Next.js 13 (app router) with this incredible library! The website is also open source at https://github.com/zolplay-cn/website here. But overall, I'm super satisfied! Appreciate for all the amazing work on the full i18n support! |
@CaliCastle Thank you for the kind words, I really appreciate it! 🙌 I had a look at the Zolplay website, what a cool website! The animated page transitions are 👌 I also looked around your code, looks really good! FYI, in regards to your I noticed that you use the domain-based routing feature. I just shipped some middleware enhancements in
Definitely feel free to open an issue in case you find something that you think could be improved!
I haven't seen that particular one, but I occasionally see hydration errors from Next.js 13—I guess they are still ironing out the RSC support. If you can track back an issue to |
@amannn I've just updated next-intl to Also noticed some speed bumps in local dev too, high five all around! Thank you! |
Great to hear! 👏 Also, thank you so much for your generosity to provide sponsoring for |
You definitely deserve a sponsor ❤️ and I was surprised you don't have one yet, a truly well developed library and I hope Next.js acquires it soon. |
Hi, With the new domain routing in @2.12.0-beta.5 the very good idea that the locale !== language has been lost. For example we have a some-site.ca with some canadian specific services and en and fr languages. So, locale is the "ca", languages are in ["en", "fr"] with the "en" as default. In parallel we have a some-site.us with a US specific services and en and es languages. The routing should be like: some-site.us/ -> "en home page" Is it possible to return the above behavior? :) |
Hi @Alex17000, that's a great point, I overlooked this. I'll look into this, maybe you can stick to an earlier beta version in the meantime? You can leave feedback for the RSC integration in #149 btw. |
Hi, which beta version has support for multiple locales per domain? We have 2 domains, one .nl and one .be. .nl only has a dutch locale, .be has flemish and french. Thanks for the help. |
@Alex17000 @DdeGooijer Proper support for handling multiple locales per domain just landed in To other people finding this thread: Please leave feedback for the RSC integration exclusively in #149 and not in this thread—thank you! |
Thanks to the team working on next-intl, we are currently using in our production MVP apuama.app, hope to be able to help supporting the project soon! |
@shadowlik That's so cool! I'm a passionate runner myself, keep up the good work! 🙌 |
Seems like a go to library for Next.js App Router per their docs https://nextjs.org/docs/app/building-your-application/routing/internationalization. I hope it would be long lived :) Edit: We are currently researching possible solutions but |
Does this mean next 13.4 has internationalization out of the box without using next-intl? |
Sure! There's a guide in the docs that describes an integration with Crowdin: https://next-intl-docs.vercel.app/docs/localization-management. Full disclosure: Crowdin is the sponsoring partner of |
Is there an example of integrating next-intl with crowdin js api? We want to have translation hosted on management platform and update them on the fly. I just saw the example that has integration with Github to make automatic merge requests. |
I haven't personally looked into integrating with the Crowdin JS API but it should certainly be possible. In the places where in the documentation a JSON file is loaded from the repository, you'd use the Crowdin API instead. |
We're using |
@lachlanjc Oh wow, that's so cool! Really happy to see Keep up the good work! 🙌 |
www.triptojapan.com - RSC beta, Crowdin and Dato CMS integration, human translations for UI and some Microsoft Azure machine translations for content, which will be eventually QA'd. |
Hello from Self massage robot. We're using next-intl. Thanks so much https://www.selftime.io |
Hey folks 👋 I'm one of the collaborators behind Node.js, and we love From all the i18n solutions out there for React and Next.js, so far the API and the design of |
@ovflowd Oh my god, that's soo cool to hear! Thank you so much for leaving a note here! And definitely reach out in case you run into something that you think can be improved! |
Thank you, @amannn! I'd say so far it has been a smooth ride, but here are 2cents if I could share:
|
Besides those comments above, fantastic work done here! (Also apologies for the poorly written comment, somehow decided to write that minutes before settling for the day 😅) |
@ovflowd Thank you for the detailed feedback, this is really helpful! To address your points in order:
Definitely feel free to open separate issues for these points to discuss in more depth if you like! |
|
Hi @amannn! I'm Dawid, Frontend Engineer at Doist, creators of Todoist and Twist. We deeply care about internationalization. Our websites, apps, and materials are translated to almost 20 languages. For weeks now, we struggled with the bug in Next.js that stops us from using Pages Router and App Router at the same time (that thing with With the release of Thanks a ton for working on this project 🙌 |
Hi @dmgawel, that's so cool to hear, Todoist looks absolutely stunning! 🙌 I noticed you have a completely distributed team at Doist, I'm sure you take i18n very seriously! :) Yep, the built-in Let me know in case you run into something! If you're interested, we could feature Todoist in the |
It's one of my go-to libraries with Next.js. I still can't believe how few star counts this library has! I found it while we were building our final project in a bootcamp and suggested it to as many people in the bootcamp as possible. I'll publish an article to share it with more people, thank you Aman and all other contributors! |
@amannn I'm happy to let you know as of today todoist.com runs on
The example was indeed very helpful! I encountered one or two problems, but I'll open separate issues to keep this one on topic :-)
Absolutely, feel free to do so! |
Subdomain based |
Leveraged it in my portfolio site using locale URL param and localized pathnames. |
|
Thank you for the amazing library. We are using it on our AI website. AR: https://www.gulfpicasso.com |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
I see nodejs web site also use |
We have been using next-intl for 14 months on our webapp, currently pinned to 3.0.0-beta.7 but I'll try to upgrade now that we can use it without having it in the url 😄 |
Had to laugh a bit too hard when I saw this, I guess I can relate 😂
That's a really cool project, thanks for sharing! Let me know if all goes smooth with migrating to the provided locale setup, I think the biggest change here is that you'll have to do a bit more yourself (e.g. setting a cookie), but overall this should reduce complexity 👍 |
It's done ! Positive things :
There's a thing that was a bit hard for me: I had the error "Unable to find next-intl locale because the middleware didn't run on this request." and didn't understand why. When I was using the beta version, next-intl was reading a cookie as a fallback when using But I don't think many people will fall in this problem because I guess (hope) I was the only person that pinned a beta version from 14 months ago 🤣 Thank you for this library! |
@raphaelbadia Awesome, glad to hear if things went mostly smoothly! 🙌 I've replied via a Twitter DM, I think there might be a chance for further simplification on your end if I'm not mistaken … I've also added some clarification for the middleware error in 99a3545, many thanks for noticing & reporting!
|
Next-intl is awesome! Hah, although it doesn’t fully support Next.js 15 yet. 😄 However, we do have a small question. When using Here’s our middleware setup: export default createIntlMiddleware({ export const config = { |
We have been using it in adam.ai for month now in production, Thank you very much for the great library |
@amannn Hello from China. I want thank you first! next-intl is really easy to use, the out-of-the-box experience greatly improved my development efficiency, and you are considered almost all of my usage scenarios (I switched from i18n routing to non-i18n routing midway through my development.). Here is my usage: |
Hi @amannn, Landing page: https://magic-portfolio.com Thanks for creating this library! |
https://www.supafriends.com is using it! And is highly active in making feedback to next-intl (best i18n tool found so far, I've even used |
Thank you for all your efforts so far. I would like to inquire about implementing internationalization in the latest next-intl 3.22V when using a basePath. Specifically, how will the URLs be affected in such a setup? Would this be something that can be managed within the middleware, or does it require additional configurations? |
@Alex-Cronotime All the relevant information should be here: Other than that, please also check the Next.js docs if you haven't used the feature yet. |
Hi from Japan !! We run a website called PeakX, which is a VTuber database. We use next-intl's locale routing on all pages. We currently provide services in two languages, Japanese and English, and plan to add more languages in the future. It's a really easy-to-use library and one of our favorites. We plan to continue using next-intl in the future 😄 |
Since the usage of this library is growing, I'm really curious which companies are using
next-intl
. Leave a comment here ifnext-intl
is helpful to you! 🙂The text was updated successfully, but these errors were encountered: