Open EdenTurgeman opened 4 years ago
I've run into this problem unrelated to this project. Webpack can use a lot of memory compiling Typescript. I've solved it by including these options in my storybook script in package.json NODE_OPTIONS='--max-old-space-size=4096'
it increases the memory node is allowed to allocate significantly (I think the default is 1024)
@UberMouse Hey, did you manage to get this to work with storybook? Because even after adding this param my problem persists and storybook doesn't seem to even pay attention to this option.
"watch": "start-storybook -p 7071 -c .storybook NODE_OPTIONS=--max-old-space-size=4096"
Seems that the memory stays at 2k or am I looking at the wrong thing
You need to add the options to the command slightly differently, here is my script command for reference
NODE_OPTIONS='--max-old-space-size=4096' NODE_ENV=storybook start-storybook -s matai -p 6006
@UberMouse Looks like I got it to work but the image I uploaded is still relevant afterward:
NODE_OPTIONS='--max-old-space-size=4096' NODE_ENV=storybook start-storybook -p 7071 -c .storybook
Looks like the limit is still in place, did you manage to make it work?
I've been using
react-docgen-typescript-loader
ever since@storybook/addon-docs
came out. Recently whilst upgrading to the beta and eventually to the stable5.3
i've experienced major performance issues where compile times are way longer. Now that would be one thing but recently my project started not compiling at all and running out of memory while trying to serve webpack, all those problems make storybook unusable right now and made me disable the plugin after trying seemingly everything.Here is my out of memory error:
My
main.js
:My
preview.js
:My
Webpack.config.js
: