Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Potentially address warning from @formatjs/intl about not pre-compiling messages #539

Open
achou11 opened this issue Jul 24, 2024 · 0 comments · May be fixed by #582
Open

Potentially address warning from @formatjs/intl about not pre-compiling messages #539

achou11 opened this issue Jul 24, 2024 · 0 comments · May be fixed by #582
Assignees

Comments

@achou11
Copy link
Member

achou11 commented Jul 24, 2024

I introduced the usage of defaultRichTextElements via #531. Since then, we get the following warning:

[@formatjs/intl] "defaultRichTextElements" was specified but "message" was not pre-compiled. 
Please consider using "@formatjs/cli" to pre-compile your messages for performance.
For more details see https://formatjs.io/docs/getting-started/message-distribution

We process messages for usage in the app but do so without using @formatjs/cli (via build-translations.mjs). Think there's a path for using the CLI with a custom formatter (if one for crowdin + our specific needs doesn't exist), but would need to look further into it.

For now, doesn't seem to be a huge issue but would be nice to address if it's straightforward.

@achou11 achou11 changed the title Potentially address warning fomr @formatjs/intl about not pre-compiling messages Potentially address warning from @formatjs/intl about not pre-compiling messages Jul 25, 2024
@achou11 achou11 self-assigned this Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant