-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Out of memory after migrating from 3 > 4 #15785
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
Comments
Hey! We haven't come across memory issues like this, thanks for reporting! It's hard to help without a reproduction or memory logs. One idea is to collect a memory trace in Node.js so we can figure out what type of variables are created that cause the memory limit to overflow. |
Will see what I can do with the article you shared. |
@bjornharvold Hey! Was just wondering if you had time to look into a memory profile or if you can share the repro? |
We have an outstanding ticket on our end to upgrade to 4.x. We have been swamped with other tasks. Will get back to this "shortly". 🙏🏻 |
I created a demo project here with Nx and Tailwind 4 https://github.com/bjornharvold/nx-tailwind-4 It contains an Nx application with an Nx buildable library. This demo works as expected and does not blow up. I have been unable to create any sort of heap dump to investigate. Looking at the docs you shared. Here is the only thing I get when starting the app. No dump files get created.
|
We're also hitting this during builds when using Astro and the Vite plugin very consistently - let me know if there's any way to get a better report / snapshot!
|
What version of Tailwind CSS are you using?
v4.0.0
What build tool (or framework if it abstracts the build tool) are you using?
For example: Angular 19
What version of Node.js are you using?
For example: v22.0.x
What browser are you using?
For example: Chrome
What operating system are you using?
For example: macOS
Reproduction URL
NA
Describe your issue
We have a 2000+ module monorepo where a few 100 of these modules use Tailwind 3.x and are built as libraries with Nx.
Then we tried migrating.
npx @tailwindcss/upgrade@next
Tried to run one of our Tailwind apps. It takes forever to build and it eventually fails with an out-of-memoy error:
Not really sure what else to report. Guessing it's the number of modules that causes this. Works great with Tailwind 3.x.
Looking at what the migration tool did was change our libs from this:
to this:
And our app css from this:
to this:
Reverting back to v3 for now.
The text was updated successfully, but these errors were encountered: