Open FilipJurkovic opened 11 months ago
I just encountered a very similar issue. In my case, I upgraded to Next 13.5, and I'm getting Maximum call stack size exceeded
when I try to build the project for production with the material-tailwind Dialog included.
I have the same issue. I managed to work around it by using an older version of next
"next": "13.5.3",
Anything newer than that gives me the same Maximum call stack size exceeded
error
I have the same issue. I managed to work around it by using an older version of
next
"next": "13.5.3",
Anything newer than that gives me the same
Maximum call stack size exceeded
error
Thank you, 13.5.3 is working for me, as well
I've faced same issue
I've faced this issue with Button component
I have the same problem since NextJs v 3.5.4. Downgrade is not the solution in my case, so I decided to drop material-tailwind...
I had the same issue and downgraded to next@13.4.9
and don't run npm audit fix
or npm audit fix --force
after downgrading. This is just a temporary solution as I wait for @material-tailwind/react
to be updated . You can check my code and the live production link at github-code & live-production-demo
I've been following https://github.com/vercel/next.js/issues/56614 - does the latest Next.js canary fix the issue for anyone? It does not for me.
When using Material Tailwind, downgrading the next version to 13.5.3 solves the problem. 13.5.4 or higher will cause an error. v13.5.7-canary.9 as well.
Can you assign this issue to me?
I'm still faced this error with material-tailwind@2.1.4 + nextjs@13.5.6. but downgrade nextjs to 13.4.19 work well.
More info: npm run dev
is work well, but npm run build
will raise error
@kdy1 I see the issue in nextjs repo is closed but, it seem not. btw thank your hard word.
@alexews v13.5.7-canary.16
will work.
@alexews
v13.5.7-canary.16
will work.
Yeah, great, confirmed it works with v13.5.7-canary.16 and also latest v13.5.7-canary.25 without this regression ;)
Thank you for capturing these details, folks. I ran into this, downgrading didn't help much, but v13.5.7-canary.25
works.
I am facing this issue with following versions:
Note: Issue resolved after downgrading next version to 13.5.3
I'm facing this issue with the version: "next": "13.5.6"
Issue resolved after upgrading to version: "next": "14.1.0"
🇧🇷🇧🇷
Hi all, I am using Material Tailwind components with Next JS 13.4 with App router and server components as per instructions in the Material Tailwind docs. Everything is running well locally but when trying to build the app and send it to vercel I encountered a strange error and have been stuck for 3 days, I will copy the terminal logs here:
Since this I have tried to logically remove parts of the app and even switched to Daisy UI for testing and I have concluded that this is a Material Tailwind issues. I was wondering if anyone else is struggling with this issue and what have you done about it.
Kind regards, Filip Jurković