May 2, 2025 at 7:04 AM
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)
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)
May 2, 2025 at 6:43 AM
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)
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)
May 2, 2025 at 6:43 AM
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)