Heap out of memory

[P4sca1]

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?

[danielroe]

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.

[P4sca1]

I am using the nuxt top level option sourcemap: false. Do I need to disable source map generation separately for nitro?

[danielroe]

Yes. I don't believe the top level option is implemented yet for Bridge.

[P4sca1]

Setting sourceMap: false in the nitro configuration did not help.

[P4sca1]

I was able to reduce the memory usage by more than 1GB.
Previously, I imported icons from the FontAwesome 6 icon library via

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 .output/server/chunks/app/server.mjs file, which has grown to a size of more than 9MB.
I expected only used icons to be included in the file, which did not work for some reason.
After updating my code to import icons differently, only icons that are used get imported in the server.mjs file and the icons are not written into the server.mjs file directly (but are imported).

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.

[AndreyYolkin]

This is what I am talking about here: #379 , will try to disable sourceMaps, too

[JuliWolf]

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 Javascript Heap out of memory

set sourceMap to false did not help

[danielroe]

Would you try #421 (comment) and see if this helps?

[AndreyYolkin]

I tried it and build time drastically reduced!
Heap usage reduced to 6Gb, too. It's a big, but this is related with rollup keeping information strategy as far as I know