Brijesh Bittu

cc: @acemarke.dev @sebmarkbage.calyptus.eu

different value somehow that'll how the classes are generated. Even if I have somthing like

const useCache = React.cache(() => ({
}));

This essentially ties the code to this particular cache which the user can't really override.
Note that Emotion is just an example I used (3/3)

your app in CacheProvider through which, you can customize the generated class name's prefix. Emotion's code calls useCache() and gets its value (default or user provided) through a context. But in case of RSCs, I can't have similar useCache() that the user can provide a (2/3)

Hey @react.dev and @nextjs.org teams, Is there a recommended approach to contexts for RSC ? With it, a library could write a singleton-like code which the user of the library could customize by providing a different value through a context. For example, in Emotion, you can wrap (1/3)