You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[nextjs] Update the withPigment API to accept config
through `pigment` key from the nextConfig object itself instead of as a
2nd argument to the call. This is a standard approach followed by other
nextjs plugins
Fixes: mui#83
> The previous API to configure theming was to pass the data in the above `pigment` key as the second argument, ie, `withPigment(nextConfig, pigmentConfig)`. But it has been changed to follow what Next.js community follows.
556
+
556
557
### Accessing theme values
557
558
558
559
A callback can be used with **styled()** and **css()** APIs to access the theme values:
@@ -572,11 +573,9 @@ Pigment CSS can generate CSS variables from the theme values when you wrap your
'Passing Pigment CSS config through the 2nd argument is deprecated and will be removed in a future stable version. Instead, pass the config through the `pigment` key in your next.js config.',
23
+
);
24
+
}
15
25
if(process.env.TURBOPACK==='1'){
16
26
// eslint-disable-next-line no-console
17
27
console.log(
@@ -103,4 +113,4 @@ export function withPigment(nextConfig: NextConfig, pigmentConfig?: PigmentOptio
0 commit comments