You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if it's a problem of this project, but at least it seems to be related.
When using storybook with this addon, everything builds normally, but an error gets thrown at runtime:
index.js:39 Uncaught Error: Accessing nonexistent addons channel, see https://storybook.js.org/basics/faq/#why-is-there-no-addons-channel
at AddonStore.getChannel (index.js:39)
at muiTheme (muiTheme.js:48)
at Object.<anonymous> (config.js:12)
at Object.defineProperty.value (config.js:19)
at __webpack_require__ (bootstrap 21742c234614f94ef929:678)
at fn (bootstrap 21742c234614f94ef929:88)
at Object.window.STORYBOOK_REACT_CLASSES (ReactPropTypesSecret.js:12)
at __webpack_require__ (bootstrap 21742c234614f94ef929:678)
at bootstrap 21742c234614f94ef929:724
at preview.bundle.js:728
getChannel @ index.js:39
muiTheme @ muiTheme.js:48
(anonymous) @ config.js:12
Object.defineProperty.value @ config.js:19
__webpack_require__ @ bootstrap 21742c234614f94ef929:678
fn @ bootstrap 21742c234614f94ef929:88
window.STORYBOOK_REACT_CLASSES @ ReactPropTypesSecret.js:12
__webpack_require__ @ bootstrap 21742c234614f94ef929:678
(anonymous) @ bootstrap 21742c234614f94ef929:724
(anonymous) @ preview.bundle.js:728
Opening muiTheme.js on line 48 reveals that it indeed accesses an addon channel.
@lightningboss sorry for late answer
this kind of bug happens when you have two different versions of @storybook/addons
if it's this case you can remove both and install the latest.
Nevertheless, I updated dependencies, so after updating this addon and storybook to the latest versions it should works fine
Hello there,
I'm not sure if it's a problem of this project, but at least it seems to be related.
When using storybook with this addon, everything builds normally, but an error gets thrown at runtime:
Opening muiTheme.js on line 48 reveals that it indeed accesses an addon channel.
My
addons.js
looks like this, nothing special:and my
config.js
like this:What do you think is the problem? Even when not loading any stories this seems to happen. Thank you very much!
The text was updated successfully, but these errors were encountered: