intlc
intlc copied to clipboard
Compile ICU messages into code. Supports TypeScript and JSX. No runtime.
With the `tsx` backend we currently type everything relevant as `ReactElement`. This generally makes sense as it's stricter than `ReactNode`, however we actually could permit consumers to return `ReactNode` in...
This usually isn't a problem, however in some environments such as AWS Lambda, or as I'm learning NixOS, it is. Looking at the 0.3.0 release Linux binary: ``` $ ldd...
Current output: ``` translations.json:3:29: | 3 | "message": "Some words {mySelect, select, other {}} {myCardinal, plural, =1 {} =1 {}}" | ^^^^^^^^ redundant-select: Select named `mySelect` is redundant as it...
The current Web workflow works pretty nicely with intlc able to compile everything in under a second, but it adds some extra moving parts separate from the main builds. What...
Tree-sitter? See also #185 (https://www.reddit.com/r/ProgrammingLanguages/comments/t4c8ms/what_parsing_techniques_do_you_use_to_support_a/hyxj3a8/).
This could be fun. Doable now with the parser keeping source information. Could inform you during editing of any linting issues, or any parsing failures.
stdin
This would be useful for sharing reduced test cases and experimenting, so we can't have to create files on disk. I believe we used to have this?
As a starting point a formatter at `intlc format` which simply parses each ICU message in a dataset and compiles them back out, which would normalise spacing. It could then...