Can it be used without the [locale] folder?

[sawa-ko]

Actually I want to use this library but I don't want to use the [locale] folder, I don't know if there is a cookie based way or something like that.

I hope you can help me.

[amannn]

Please see #960!

[amannn]

Is that during development or production? next-intl includes additional warnings during development that might be helpful. Are you by chance using the navigation APIs?

Currently, this feature is intended to be used with the following assumptions (as mentioned in the PR):

1. No [locale] segment needs to be added
2. No middleware needs to be configured
3. The navigation APIs from next-intl don't need to be used
4. Static rendering works without tradeoffs

I'm having a look if I can support the navigation APIs nonetheless or at least provide better error handling.

[sawa-ko]

Hum, I have them declared but I don't have them using, and it is in development that the error message is displayed.

To be honest, I haven't noticed if there are any warnings on the console, I'll check.

[sawa-ko]

Yes, it seems that I had it imported in a component and I have removed it and it seems that it has been solved. A bit weird, not sure if that was the problem.

May I make a suggestion or ask a question? Why is the typing not working here or is it not typed?

[amannn]

Great to hear if that fixed the issue for you! 🙌

Hmm, interesting that you don't see any completions there, theoretically it should work:

Note however that locale is not included in the types yet for the release you're using, I noticed that after the pre-release and have fixed it in 2375929.

[sawa-ko]

Great, and it seems to be working fine, I've been testing it for a couple of hours and haven't encountered any message problems. 💯