Jan Amann

Hey, there's been some previous discussion on this here: https://github.com/amannn/next-intl/discussions/456 To [some extent](https://github.com/amannn/next-intl/discussions/456#discussioncomment-12072349), you can already use other tools define and extract messages from a component. I've recently started [wondering](https://github.com/amannn/next-intl/discussions/456#discussioncomment-12651813)...

That's really cool! Have you thought about the API yet? I was thinking about something along these lines: ```tsx import {useTranslations} from 'next-intl/extracted'; // Or as a separate lib: //...

That's really cool! I really haven't made my mind up here, so I'm happy to see any other perspectives. Definitely leave a note here once there's something to play with!...

There are no immediate release plans here, sorry. I'm planning to explore this topic further later this year, but it will take a bit of time—sorry. If you rely on...

Hi everyone following along here! I'm happy to share a first draft of an RFC I've written up for first-class message extraction support in `next-intl`: → [Rendered version](https://github.com/amannn/next-intl/blob/feat/message-extraction/rfcs/001-message-extraction.md) → [Discussion](https://github.com/amannn/next-intl/discussions/2036)...

Closed by #2080 **Learn more:** - [Blog post](https://next-intl.dev/blog/use-extracted) - [X post](https://x.com/jamannnnnn/status/1986815227816456398) - [Bluesky post](https://bsky.app/profile/amann.work/post/3m52f7fv3rk26)

I absolutely agree, would be great to add some docs for this! We can use this issue for the time being to collect content ideas. I think one of the...

Interesting, could definitely be worth considering—thanks for the report! This will need some investigation first, e.g.: 1. Check if `intl-messageformat` supports strings for numbers in messages. We had a similar...

One implication of this in combination with https://github.com/amannn/next-intl/pull/1499 would be that we can currently do this ([ref](https://x.com/jamannnnnn/status/1859143968904319352)): ```tsx "{count} followers" // ^? {count: string} "{count, number} followers" // ^? {count:...

A note from https://x.com/SlexAxton/status/1859242191408746751 on support of string-based numbers in Format.JS: > it does support them i think, just the types are wrong Might be worth checking if this is...