[Bug]: Javascript heap out of memory when doing build-storybook when using docgen: 'vue-component-meta' #26647
Comments
|
I just encountered the same problem. I can build it locally, but not on CI, probably because the project is not as big yet. I think it's related to using "html types" like
Looking at the content, it seems like it pulls the MDN documentation into it for some reason:
I had to switch to |
|
We also just switched to |
|
this will cause error on vercel: |
|
Hey @larsrickert the issue I'm getting this with is a private repo with 70 Vue + TS components, none of which being too complex (also each being < 200 lines of code). It's a private repo so I'll try and generate something anonymised based on it, but hopefully the above is helpful. |
|
@larsrickert I quickly created a more isolated test component I can share: CTest.vue: CTest.stories.ts: And this results in a 38mb big file when built: |
Thanks! The issue seems to be the In the meantime, using Example: export interface CTestProps {
triggerRef: Pick<HTMLElement, "addEventListener" | "removeEventListener">| null
} |
That's good to know, thanks! I think for this particular case this doesn't work, as we want to generally limit the prop type to an HTMLElement or VueComponent, but it might come in handy in other cases. I guess all types "exposed" to storybook are affected by this problem, not just props. The |
|
I have the same issue with import type { HTMLAttributes } from 'vue'
export interface ComponentProps extends /* @vue-ignore */ HTMLAttributes {
...
}This causes the build to create massive files with all the docs from the
|
Describe the bug
Hi folks - Storybook is amazing and I ❤️ it - and I'm very happy that 'vue-component-meta' was added in Storybook 8.
I migrated my component library to Storybook 8 recently and although the development build (
storybook dev -p 6006 --no-open) works without issue - the build (npx storybook build) fails locally and in CI due to running out of memory (see below).Removing
docgen: 'vue-component-meta'from the Storybook configuration resolves the issue - but this docgen is the main reason I've migrated across.It fails while transforming the .ts & .vue files - so I'm wondering if it's doing something while bundling (which isn't necessary) that isn't happening when running in the dev build which would be fine to just have built instead.
The component library I'm building has ~75 Vue3 components and in Storybook 8 without vue-component-meta it would use ~1.7GB.
I've tried going up to as far with max_old_space_size as 16GB to even get it to build locally but to no avail. My CI provider allows up to 4GB so that would be the goal.
main.ts
Trace just before crash:
Trace after crash (running with --max_old_space_size=16384 to try to saturate my RAM):
To Reproduce
See bug description
System
Storybook Environment Info: System: OS: macOS 14.2.1 CPU: (8) arm64 Apple M1 Pro Shell: 5.9 - /bin/zsh Binaries: Node: 18.17.0 - ~/.nvm/versions/node/v18.17.0/bin/node Yarn: 1.22.19 - /opt/homebrew/bin/yarn npm: 9.6.7 - ~/.nvm/versions/node/v18.17.0/bin/npm <----- active pnpm: 8.9.2 - ~/Library/pnpm/pnpm Browsers: Chrome: 123.0.6312.59 Safari: 17.2.1 npmPackages: @storybook/addon-essentials: ^8.0.4 => 8.0.4 @storybook/addon-interactions: ^8.0.4 => 8.0.4 @storybook/addon-links: ^8.0.4 => 8.0.4 @storybook/blocks: ^8.0.4 => 8.0.4 @storybook/vue3: ^8.0.4 => 8.0.4 @storybook/vue3-vite: ^8.0.4 => 8.0.4 chromatic: ^11.0.0 => 11.0.0 storybook: ^8.0.4 => 8.0.4Additional context
No response
The text was updated successfully, but these errors were encountered: