@storybook/addon-actions@npm:6.5.0-alpha.64 causes configuration error #17996
Comments
|
I'm also getting the exact same issue with 6.3.8 too and webpack 4 |
|
More details: started failing at Logs |
|
This seems to be stemming from when the presets returned from this https://github.com/storybookjs/storybook/blob/next/lib/builder-webpack5/src/preview/iframe-webpack.config.ts#L79 returns an empty object |
|
Had the same issue pop up here when upgrading from The reason the issue popped up for us seems to be related to We tried several configurations, the following failed: module.exports = {
stories: [ ... ],
addons: ['@storybook/addon-essentials'],
}The following configurations worked: module.exports = {
stories: [ ... ],
addons: [{
name: '@storybook/addon-essentials',
options: {
'actions': false,
}
}],
}module.exports = {
stories: [ ... ],
addons: ['@storybook/addon-actions', '@storybook/addon-essentials'],
}module.exports = {
stories: [ ... ],
addons: ['@storybook/addon-docs', '@storybook/addon-controls', '@storybook/addon-actions', '@storybook/addon-backgrounds', '@storybook/addon-viewport', '@storybook/addon-toolbars', '@storybook/addon-measure', '@storybook/addon-outline'],
}Because we were able to load every add-on separately without issue we believe the issue might be related to how System information |
|
thanks to @nbelzer , I also solved the problem by explicitly adding ref: https://github.com/MH4GF/log.mh4gf.dev/pull/190/files Since this is a public project, I'll also post the chromatic build error log for reference. |
|
@MH4GF can you please share how to reproduce in your project? would be useful to have a repro as we do a proper fix |
|
@shilman Can be reproduced in this PR and branch. |
|
Hey, Today I wanted to upgrade Steps to reproduce:
I'm on |
|
@MH4GF I think your issue is the unusual way you have your SB dependencies listed: If you look in @bobbonius you cannot update a single storybook package, we publish all versions of each package and expect them to stay in sync. The TLDR is this problem is caused by conflicting versions of various SB packages. @shilman we should add something to the CLI to check for this situation and complain loudly :) |
|
@tmeasday thank you! Worked out now 🎉 |
how did you solve this? |
|
@yannickrocks the workaround appears to be adding the affected addon manually before essentials: |
|
I couldn't see my So this does not work for me (storybook builds successfully but no addon will be visible) module.exports = {
addons: [
'@storybook/addon-actions'
'@storybook/addon-docs'
'@storybook/addon-viewport',
'@storybook/addon-controls',
'@storybook/addon-toolbars',
'@storybook/addon-measure',
'@storybook/addon-outline',
]
}This works for me: module.exports = {
addons: [
'@storybook/addon-essentials',
]
}Adding any addon before essentials makes that addon hidden in UI!! Again with no errors. module.exports = {
addons: [
'@storybook/addon-viewport'
'@storybook/addon-essentials',
]
}I'm using yarn 3 and pnp. My issue also looks like #8383. |
|
Maybe my method can fix someone's problem. Before: {
"xx": {
"@storybook/addon-actions": "^6.4.13",
"@storybook/addon-essentials": "^6.4.13",
"@storybook/addon-links": "^6.4.13",
"@storybook/vue": "^6.4.13",
}
}Actually in node_modules，I found package version is 6.15.X . So I limit the semantic version like this. After {
"xx": {
"@storybook/addon-actions": "~6.4.13",
"@storybook/addon-essentials": "~6.4.13",
"@storybook/addon-links": "~6.4.13",
"@storybook/vue": "~6.4.13",
}
}Then This way work for my problem. |
|
I had the same problem and after messing around I found that adding {
addons: [
'@storybook/addon-knobs',
'@storybook/addon-actions/register',
'@storybook/addon-notes',
'@storybook/addon-storysource',
],
} |
Describe the bug
Adding
@storybook/addon-actions@npm:6.5.0-alpha.64to theaddonsin the configuration results in an error.To Reproduce
package.jsondeps (nextis currently6.5.0-alpha.64):main.js:run command:
results in error:
Removing
@storybook/addon-actionsfrom theaddonsarray fixes the error.System
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: