Eemeli Aro

Yeah, this feels like a bug, and rather unlikely to affect real-world users in a way that anyone would (should?) depend on.

I've been thinking that it might be worthwhile to put together proper Next.js support; it's not just the React part that's got a bit of an impedance mismatch, but the...

You're right, on both counts. The "root cause" you identified is almost certainly the culprit here, and I'm pretty sure that those lines could now be dropped. They're really a...

@cdaringe Apologies for being so late getting to this, as it's actually an entirely separate issue from the one in the parent thread. There's an oblique reference to this "feature"...

I'm considering an additional minor-level fix for this by expanding the `--simplify` option to provide more choices, but keeping that to not also be a breaking change is currently blocked...

Hmm, apparently the `compileModule` types and docs are a bit misleading, as this actually already works: ```js const mf = new MessageFormat('en') compileModule(mf, "{ count, plural, =0 {{formattedCount} Products} one...

That's still missing the bit where during the build you get the info about index 0 having an English message and index 1 having a German message. As you'll need...

This is almost certainly an issue with how you're using `ngx-translate-messageformat-compiler`; would suggest asking there for help? This in particular might be relevant: https://github.com/lephyrus/ngx-translate-messageformat-compiler#locale-initialization

You should be asking these questions in that project.

A PR fixing this to the "expected" result would be most welcome.