search

QuiiBz / next-international

Type-safe internationalization (i18n) for Next.js
https://next-international.vercel.app
MIT License
1.19k stars 52 forks source link

next-international V2 #359

Open QuiiBz opened 4 months ago

QuiiBz commented 4 months ago

next-international V1 has been released 6 months ago, and continuously improved to add more features and fix bugs.

There are however some recurring issues that can't be fixed without large breaking changes. Here's an overview of the main issues that I and the community noticed:

Chaining the middleware

94, #187, #326, #341, #354

Translating not-found.tsx / error.tsx

268, #288, #357

Testing

178, #323, #348

Misc

343

Documentation

The documentation can sometimes be hard to navigate around and find what we're looking for, especially around the available configuration options.

What about now?

I'll progressively update this issue to add solutions and possible improvements.

The focus points for the V2 are:

How can I help?

Thank you so much for wanting to help us on this release! The first step will be to define exactly the things we need to tackle: we'll create issues for each of these task, and they'll all be under the 2.0 milestone.

Development will start soon in a separate branch. In the meantime, please share your experience, positive or negative, and things that you would like to see improved/added/fixed.

fi5u commented 4 months ago

Hi, thanks for this.

I'm in the process of moving my project over from next-localization to next-international. The only feature that I've noticed that I'm missing is the ability to return an object (or array) of translations. This useful for example when different languages have different requirements – it's something I've used extensively in next-localization.

I would imaging this feature being turned on from an option on useI18n / useScopedI18n.

By the way, I liked the simplicity of the documentation – it was very quick to get set up with it.

gustaveWPM commented 4 months ago

Hello, nice to know! I was just having trouble here: https://github.com/QuiiBz/next-international/issues/369#issuecomment-1978018322

I'm looking forward to hear about this V2. :)

addlistener commented 2 months ago

One thing I think we can do is better naming

I choose next-international because of its typescript native approach so a lot of features

are already there as pure typescript code. No need to mess with configurations

If we have a better naming people can easily distinguish us from other libs. Check out the mess here (https://www.reddit.com/r/nextjs/comments/1c7xc6e/whats_your_i18n_lib_choice_with_nextjs_and_why/) Maybe sth like next-typescript-international?