Replies: 2 comments 1 reply
-
Hey! Are you sure the servers are identical? This leads me to believe that either the node versions are different or the servers have different amounts of RAM. Without a clonable reproduction I might not be able to help too much here. My guess though is that safe lists are involved. Generally when the process runs out of heap memory and it's looks to be because of Tailwind generally it's due to a safelist configuration including an extremely large number of classes. In this case, Tailwind itself usually does an okay job of generating the CSS but tools like webpack, cssnano, etc… (and even your browser sometimes) has a hard time handling such a large amount of CSS. I poked around flow bite a bit and it's using Any chance you could provide a reproduction? If so please link it and @-mention me and I'll take a closer look. |
Beta Was this translation helpful? Give feedback.
-
Seems there are still memory leaks. Using watch works for awhile but then ultimately crashes
Rebuilding... <--- Last few GCs ---> [36228:000001BDB1820080] 8234176 ms: Mark-Compact 4051.5 (4138.6) -> 4040.2 (4143.1) MB, 1462.72 / 0.00 ms (average mu = 0.805, current mu = 0.108) allocation failure; scavenge might not succeed <--- JS stacktrace ---> FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory 1: 00007FF6A7BA72EB node::SetCppgcReference+18123 |
Beta Was this translation helpful? Give feedback.
-
Hello! Having issues with using npx mix.
Using 2 identical servers. On one server compilation without issues in seconds, on second for some reasons not.
Tailwind v3.3.3
Laravel mix latest
npx v9.8.1
Node: v18.17.1
OS: Ubuntu
Error:
Config files:
Tailwind config
app.css
Beta Was this translation helpful? Give feedback.
All reactions