Currently to add new utilities we have to define them in a file called xstyled.config.ts and then export the relevant factories to get the new utilities. But what if our codebase is huge and we have to replace all instances of @xstyled/.... to the new exported ones?
I feel like there should be a logic where the @xstyled/system either reads the xstyled.config.ts and extends the utilities accordingly or expose a function like we do with the theme, eg extendSystem, and have those utilities without exporting the custom ones.
My question is, does anyone got in that situation? If yes what was the best solution without too much overhead?
Currently to add new utilities we have to define them in a file called
xstyled.config.tsand then export the relevant factories to get the new utilities. But what if our codebase is huge and we have to replace all instances of@xstyled/....to the new exported ones?I feel like there should be a logic where the
@xstyled/systemeither reads thexstyled.config.tsand extends the utilities accordingly or expose a function like we do with the theme, egextendSystem, and have those utilities without exporting the custom ones.My question is, does anyone got in that situation? If yes what was the best solution without too much overhead?