-
-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: use derived storybookConfig as the merge base #740
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for nuxt-storybook ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Ryan Leckey <[email protected]>
3428b6d
to
f149e7a
Compare
Thanks! The changes look good to me, but the playground example ci is now failing. Could you please have a look? |
It's failing because now the typed documentation is being generated and that takes a serious amount of RAM. I'm away now but I'll try and circle back and add a NODE_OPTION to the command to up the space allowed for node. |
Even with increased heap size it fails (and increases the build time). Could you perhaps revert the type changes for now? |
I had a look at this and it turns out that it's the vue runtime compiler that is the problem. I "fixed" it by removing the vue alias, but now some of the showcase examples are empty. Do you have an idea what's the reason for the out of memory error? For me it always stops at (with the vue alias in place)
but I'm not sure if that's indeed the true problematic file. Might be fixed with storybookjs/storybook#28589, although that seems to be a different problem. |
Any news about the status? |
I'm currently waiting for storybook 8.3.0 to see if storybookjs/storybook#28589 helped here. If you want to help: revert 25e2ac5 and investigate why we run out of memory during the build of the playground |
I will check it the next few days. Storybook 8.3.0 is released 🥳🥳 |
Sadly the update to Storybook 8.3 didn't rosolved the issue. I tried to investigate it further and it seems that
(and the next time with one more appended) It's triggered by every import of vue, the first one being in |
@maximilian-schwarz did you already found the time to look into this a bit more? |
This comment was marked as off-topic.
This comment was marked as off-topic.
[
{
name: 'storybook:code-generator-plugin',
enforce: 'pre',
configureServer: [Function: configureServer],
config: [Function: config],
configResolved: [Function: configResolved],
resolveId: [Function: resolveId],
load: [AsyncFunction: load],
transformIndexHtml: [AsyncFunction: transformIndexHtml]
},
{
name: 'plugin-csf',
rollup: [Object],
vite: [Object],
webpack: [Function: webpack],
rspack: [Function: rspack],
enforce: 'pre',
transform: [AsyncFunction: transform]
},
{
name: 'storybook:inject-export-order-plugin',
enforce: 'post',
transform: [AsyncFunction: transform]
},
{
name: 'storybook:strip-hmr-boundary-plugin',
enforce: 'post',
transform: [AsyncFunction: transform]
},
{
name: 'storybook:allow-storybook-dir',
enforce: 'post',
config: [Function: config]
},
{
name: 'storybook:external-globals-plugin',
enforce: 'post',
config: [AsyncFunction: config],
transform: [AsyncFunction: transform]
},
{
name: 'storybook:rollup-plugin-webpack-stats',
enforce: 'post',
moduleParsed: [Function: moduleParsed],
storybookGetStats: [Function: storybookGetStats]
},
Promise { [Object] },
{
name: 'storybook:vue-docgen-plugin',
transform: [AsyncFunction: transform]
}
] Only the last 2 entries are different from import {
...
type Plugin as VitePlugin,
...
} from 'vite'
...
storybookViteConfig.plugins = storybookViteConfig.plugins.filter((plugin: VitePlugin) => !(plugin instanceof Promise)) |
@@ -15,9 +15,6 @@ const config: StorybookConfig = { | |||
name: '@storybook-vue/nuxt', | |||
options: {}, | |||
}, | |||
docs: { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this go in the playground/.storybook/main.ts now according to https://storybook.js.org/docs/writing-docs/autodocs#set-up-automated-documentation?
Out of curiosity, has this work been tested with the latest alpha release? I'm hoping that it'll be released in the upcoming weeks and it would be nice to have the related issues resolved. |
Any success with this ? |
any
fromtypes.d.ts
storybookConfig
over the bareconfig
when mergingShould fix #756 and fix #799 and fix #753