MUI v9 release is here 🚀
This release changes how we ship major versions.
We shipped new features and components on a coordinated major across Material UI and MUI X with one goal: make your workflows easier to build, upgrade, and scale.
Highlights and links below 👇
Published PiAgent to VSCode extensions marketplace. It a thin layer over pi-coding-agent by
@badlogicgames's pi cli but in vscode and shares the same context as the cli. It is 100% ai coded.
https://t.co/avOJLJAfyF
@poteto Bundle size increase seems to be a major issue for us at the moment - https://t.co/EqVZe23Ry9
Plus some unexpected behavioral changes that we are still debugging - https://t.co/Z0FXUn85p9
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)
Hey @reactjs and @nextjs 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)
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)
@TkDodo How would this work if *produce* was optional? Like, if it is present, the param's type to *consume* should be the return value of produce, otherwise, the param types can be another default or derived type?
@JoshWComeau@Aaron_Powell I'm late on this info, but one thing to note is that if you have configured your nextjs config with Pigment CSS, you'll be able to use imports from linaria as well.