Replies: 5 comments 4 replies
-
I would recommend turning source maps off for your nitro build. You should be able to configure in your Nuxt config under the nitro key. |
Beta Was this translation helpful? Give feedback.
-
I was able to reduce the memory usage by more than 1GB. import { IconA, IconB } from '@fortawesome/free-solid-svg-icons' This resulted in the entire icon library (around 3.200 icons per preset, I was using 2 presets) to be inlined into the import { IconA } from '@fortawesome/free-solid-svg-icons/IconA'
import { IconB } from '@fortawesome/free-solid-svg-icons/IconB' I think the memory usage is still quite high and I am wondering, why tree shaking wont remove unused icons. |
Beta Was this translation helpful? Give feedback.
-
This is what I am talking about here: #379 , will try to disable sourceMaps, too |
Beta Was this translation helpful? Give feedback.
-
Have the same issue. Starts after updating nuxt to version Nuxt CLI v3.0.0-rc.6 Client part build successfully, webpack generates server chunk and then throws error set |
Beta Was this translation helpful? Give feedback.
-
Would you try #421 (comment) and see if this helps? |
Beta Was this translation helpful? Give feedback.
-
Running
nuxi build
even without pre-rendering takes up a huge amount of memory (up to 4GB) to build the page. The webpack build works fine and takes around 1GB. But as soon as the nitro server build starts, the memory usage is skyrocketing.Because of that I can’t build my nuxt application in environments with limited memory constraints like GitHub Actions or in a Docker container.
I can’t provide a reproduction, so I started a discussion. What is your experience with nuxt bridge memory usage?
Beta Was this translation helpful? Give feedback.
All reactions