-
-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How can I custom a theme with NX+Next.js? #83
Labels
enhancement
This is not a bug, nor a new feature
support: docs-feedback
Feedback from documentation page
support: question
Community support but can be turned into an improvement
Comments
JenniferGoijman
added
status: waiting for maintainer
These issues haven't been looked at yet by a maintainer
support: docs-feedback
Feedback from documentation page
labels
May 13, 2024
zannager
added
the
support: question
Community support but can be turned into an improvement
label
May 27, 2024
This requires a change in the api of |
brijeshb42
added
enhancement
This is not a bug, nor a new feature
and removed
status: waiting for maintainer
These issues haven't been looked at yet by a maintainer
labels
May 30, 2024
brijeshb42
added a commit
to brijeshb42/pigment-css
that referenced
this issue
May 30, 2024
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
1 task
brijeshb42
added a commit
to brijeshb42/pigment-css
that referenced
this issue
Jun 17, 2024
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
brijeshb42
added a commit
to brijeshb42/pigment-css
that referenced
this issue
Jun 17, 2024
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
brijeshb42
added a commit
to brijeshb42/pigment-css
that referenced
this issue
Jun 21, 2024
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
Based on @omerman's input, the following works. Using import { extendTheme } from "@mui/material";
import { composePlugins, withNx } from "@nx/next";
import { withPigment as withPigmentNext } from "@pigment-css/nextjs-plugin";
/**
* @type {import('@nx/next/plugins/with-nx').WithNxOptions}
**/
const nextConfig = { };
/**
* @type {import('@nx/next/src/utils/config').NextPlugin}
*/
const withPigment = (nextConfig) => {
/**
* @type {import('@pigment-css/nextjs-plugin').PigmentOptions}
*/
const pigmentConfig = {
transformLibraries: ["@mui/material"],
theme: extendTheme({ }),
};
return withPigmentNext(nextConfig, pigmentConfig);
};
const plugins = [withNx, withPigment];
export default composePlugins(...plugins)(nextConfig); |
Ill check soon as well 🙏🙏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
This is not a bug, nor a new feature
support: docs-feedback
Feedback from documentation page
support: question
Community support but can be turned into an improvement
Related page
https://github.com/mui/pigment-css?tab=readme-ov-file#start-with-nextjs
Kind of issue
Missing information
Issue description
This is my
next.config.js
file that I have configured PigmentCSS in a Nx+Next.js repo:How can I custom a theme with NX+Next.js?
Context
Search keywords: NX, Next.js
The text was updated successfully, but these errors were encountered: