amann.work
Maintainer of 🌐 https://next-intl.dev · Guest lecturer for React Web Applications at FHV · Partner for User Interface Engineering
@jamannnnnn on X
93 posts
160 followers
325 following
Regular Contributor
Active Commenter
comment in response to
post
As a side note, Next.js 15 currently has a tree-shaking issue which can cause your messages to leak into the middleware bundle. The Next.js team has confirmed the issue.
More context & workaround: github.com/amannn/next-...
comment in response to
post
For context: github.com/vercel/next....
comment in response to
post
Really cool!
comment in response to
post
Super nice! 👏 Was the migration straightforward?
comment in response to
post
Thanks mate! Was really incredible light yesterday morning with the mist and all ✨
comment in response to
post
I’m really excited about that one too. 😌 Let me know how it works for you in case you give it a shot!
comment in response to
post
Guter Artikel, danke für die Tipps! Muss mir Warp mal anschauen, bin noch einer der vermutlich letzten die bei Hyper hängengeblieben sind …
comment in response to
post
Way too kind of you, thanks Matthias! 😊😊
comment in response to
post
Oh man, you’re way too kind! 😅 Just googled guachinche! 😳🤤
I’ll reply via DM!
comment in response to
post
Thats a really kind offer, will definitely keep this in mind! I’m actually visiting the canaries over new year’s to hopefully improve my Spanish a bit 🤓. Unfortunately not Tenerife this time though, would have loved to say hi to the local JS community there!
comment in response to
post
Amazing! 🙌 I’ll make sure to include a localization to Spanish in the course, I guess I better start working on my pronunciation 😄
comment in response to
post
Yep, I’d welcome that too! Or a public planning board where you’d be able to see which issues/PRs are in the pipeline, just so you can be sure that it hasn’t been forgotten.
comment in response to
post
Somewhat unfortunate that your PR still hasn’t seen a review yet … :-/
comment in response to
post
Oh no, completely missed your PR! 😅 Sorry!
comment in response to
post
Ough, sounds like a rough morning 🙈
comment in response to
post
Awesome! Would certainly be curious to have a look in case you publish it!
comment in response to
post
React 19? 😄
comment in response to
post
Pretty cool! Does it also handle partial updates, eg a single message being added/updated/deleted from the source language?
comment in response to
post
Very nice!
comment in response to
post
Still a bit early, but I have high hopes for this feature in the context of i18n and multi tenancy: github.com/vercel/next....
comment in response to
post
Ah yep, that makes sense! I think in the future you might be able to use `(await rootParams).domain` instead of the host header—that could also help to enable static rendering if that's something you're interested in.
comment in response to
post
Awesome that you were able to make it work! Would be curious about your use case though, would the domains option of the routing config work for you?
next-intl-docs.vercel.app/docs/routing...
comment in response to
post
Spannender thread, danke fürs teilen!
comment in response to
post
Intl.DurationFormat for stage 4 would be cool, currently Node.js and Firefox lack support for it 👍
Also AsyncContext for sure!
comment in response to
post
Ah—got it, thanks!
comment in response to
post
Can you call a Server Action during SSR? 🤔 I thought that’s an error last time I checked
comment in response to
post
I have to say, I’m generally struggling a bit with Bluesky to get the most relevant posts after I last logged in. Is the Discover feed the right place for this? It seems to heavily prioritize how fresh a post is. Not sure if there’s a setting I’m missing
comment in response to
post
Oh, you mean "app" as an actual part of the pathname? Sorry, I misunderstood. Yep, true, could make a difference there! Maybe more to be handled as a base path …
comment in response to
post
Hmm, not sure if I follow, but /[locale] is a dynamic segment, right? A non-dynamic segment would probably be /v1 I think. But yeah, it's still early, probably for the best to let them cook and provide docs first! 👍
comment in response to
post
As far as I know, it can handle layouts at multiple levels just fine!
comment in response to
post
As a side note, you probably heard the news about rootParams coming to Next.js? Since you've explored your fair share of static rendering with i18n, and participated a lot in discussions & ideas.
comment in response to
post
That's really cool! Yeah well, hydration performance was always quite important for me, that's also the reason why I wanted to push next-intl into the RSC paradigm as quickly as possible.
comment in response to
post
Oh no way, you tried out that next-client-script thing? Haha I made it as a PoC for a client, but we decided to go with an experimental React version instead at the time which already had non-blocking hydration 😄
comment in response to
post
Looks really clean to me, I like it a lot! 👌👌
comment in response to
post
I think so too. However, “good” or “bad” isn’t set in stone, of course you’re not a pro when you’re just starting out.
I’m honestly worried about the barrier to get “good” becoming too significant, putting people off to properly learn development in the first place.
comment in response to
post
Many thanks to github.com/jorgebef for helping me verify this as a lawyer 🙏
comment in response to
post
The updated docs will have a detailed section on this topic.
You can also check out the linked document for all details: https://ec.europa.eu/justice/article-29/documentation/opinion-recommendation/files/2012/wp194_en.pdf
comment in response to
post
Note that you can already make this change today, if desired—see https://next-intl-docs.vercel.app/docs/routing#locale-cookie
It's worth noting though that you can use a longer expiration if:
1. You inform users about the usage of cookies
2. GDPR doesn't apply to your app
comment in response to
post
🤝
comment in response to
post
Haha, thanks for the kind words! 😄 Well it’s not released yet, only teasing for now 😉