Storybook running out of memory when building

Describe the bug After upgrading from 6.0.12 to 6.0.21 when running npx http-server ./lib/storybook -p 8082 -a localhost at 69% built I get: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

Note: in the past we have had the same problem on 5.x versions, which were resolved by upgrading node.

I appreciate this lacks a lot of context, and it’s a private repo so I’m unable to share as is, but if anyone is able to point me in the direction of diagnosing or potential causes, that would be of great help.

We are running typescript.

To Reproduce Steps to reproduce the behavior:

Run npx http-server ./lib/storybook -p 8082 -a localhost

Expected behavior Builds as expected

System: Please paste the results of npx sb@next info here.

System:
OS: Windows 10 10.0.19041
CPU: (8) x64 Intel® Core™ i7-8650U Binaries:
Node: 12.16.1 - C:\Program Files\nodejs npm: 6.13.4 - C:\Program Files\nodejs\n Browsers:
Chrome: 84.0.4147.135
Edge: Spartan (44.19041.423.0), Chromiu npmPackages:
@storybook/addon-actions: 6.0.21 => 6.0 @storybook/addon-essentials: 6.0.21 => @storybook/addon-knobs: 6.0.21 => 6.0.2 @storybook/addon-links: 6.0.21 => 6.0.2 @storybook/addon-toolbars: 6.0.21 => 6. @storybook/addons: 6.0.21 => 6.0.21
@storybook/react: 6.0.21 => 6.0.21
@storybook/theming: 6.0.21 => 6.0.21

[gabrielliwerant]

This is an issue when using storybook in a monorepo (a repo containing many individual packages and their own node_modules folders). It seems that when using default configs, storybook runs out of memory because it is scanning all of the node_modules sub folders. If I remove all the node_modules folders, it works fine. Is there a recommended way to include storybook in a monorepo? I’m thinking I’ll have to use a custom webpack config that excludes the appropriate folders.

[gazpachu]

Even with 6GB of RAM in docker, the build still fails:

INFO[0062] RUN npm install --unsafe-perm --legacy-peer-deps 
INFO[0062] cmd: /bin/sh                                 
INFO[0062] args: [-c npm install --unsafe-perm --legacy-peer-deps] 
INFO[0062] Pushing layer xxxx.ap-northeast-1.amazonaws.com/.../cache:xxxxxxxx to cache now 
INFO[0062] Running: [/bin/sh -c npm install --unsafe-perm --legacy-peer-deps] 
<--- Last few GCs --->
[113:0x589ab50]   107832 ms: Scavenge 2000.0 (2067.4) -> 1997.6 (2069.1) MB, 16.8 / 0.0 ms  (average mu = 0.723, current mu = 0.475) allocation failure 
[113:0x589ab50]   107936 ms: Scavenge 2001.6 (2069.1) -> 1999.8 (2072.6) MB, 12.5 / 0.1 ms  (average mu = 0.723, current mu = 0.475) allocation failure 
[113:0x589ab50]   108042 ms: Scavenge 2005.4 (2072.6) -> 2003.3 (2091.4) MB, 16.8 / 0.0 ms  (average mu = 0.723, current mu = 0.475) allocation failure 
<--- JS stacktrace --->
FATAL ERROR: MarkCompactCollector: young object promotion failed Allocation failed - JavaScript heap out of memory
Segmentation fault (core dumped)
error building image: error building stage: failed to execute command: waiting for process to exit: exit status 139
Cleaning up file based variables
00:00
ERROR: Job failed: command terminated with exit code 1