Christophe Marchadour
@domcrashx8.bsky.social
Totally fair from that perspective.
I'm building internal libs at my company where we want everything unified so we don't let users change default placeholders etc...
We have some level of flexibility but not as much and for that reason have to handle i18n per component.
I'm building internal libs at my company where we want everything unified so we don't let users change default placeholders etc...
We have some level of flexibility but not as much and for that reason have to handle i18n per component.
November 24, 2024 at 12:16 PM
Totally fair from that perspective.
I'm building internal libs at my company where we want everything unified so we don't let users change default placeholders etc...
We have some level of flexibility but not as much and for that reason have to handle i18n per component.
I'm building internal libs at my company where we want everything unified so we don't let users change default placeholders etc...
We have some level of flexibility but not as much and for that reason have to handle i18n per component.
i18n for components sounds like an interesting topic to add to that list. Keeping the bundle size light how do you localize for a component library... :)
November 24, 2024 at 11:29 AM
i18n for components sounds like an interesting topic to add to that list. Keeping the bundle size light how do you localize for a component library... :)