Still getting "accessing nonexistent addons channel"
See original GitHub issueEven after bumping all my addons to the new version I’m still getting the non-existent addons error…
Something I found a bit interesting is how NPM installed things.
It’s like @storybook/react has it’s own version of addons?
Issue Analytics
- State:
- Created 6 years ago
- Comments:42 (18 by maintainers)
Top Results From Across the Web
Still getting "accessing nonexistent addons channel" #1981
3 and getting the non-existent channels message. I am using TypeScript and there is no addons channel at all. This behavior now is...
Read more >StorybookJS: Accessing non-existent addons channel
I am currently trying to add the @storybook/addon-console to Storybook. After running npm install @storybook/addon-console ...
Read more >Support does not exist - WordPress.org
I have been going back and forth with support about a simple issue they disregard and fail to correct. Getting support takes days...
Read more >Ensure addons Version in a Storybook Addon - Jake Trent
Non-existent Channel ... The docs describe this error's root cause as commonly being that you have two versions of @storybook/addons . If there ......
Read more >Frequently Asked Questions - Storybook - JS.ORG
Why is there no addons channel? Why aren't Controls visible in the Canvas panel but visible in the Docs panel? Why aren't the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@storybooks/team I think we really need to make
@storybbok/addonsa peer dependency everywhere except the apps. It’s a shame that we make users remove their lockfilesAhhh, I had removed
node_modules, but neverpackage-lock. Thanks!