Skip to content
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

[6.4.9] Unknown exception created by Scroller #17161

Closed
dvilchez-qatium opened this issue Jan 7, 2022 · 4 comments
Closed

[6.4.9] Unknown exception created by Scroller #17161

dvilchez-qatium opened this issue Jan 7, 2022 · 4 comments

Comments

@dvilchez-qatium
Copy link

Describe the bug
I was upgrading my storybook project from version 5.3.21 to 6.4.9. After the upgrade starting the app fails with this error:

2022-01-07 at 11 16

To Reproduce
Update storybook in a project using react 17.0.2 (I have tried to create a reproduction but the script hasn't worked for me)

System
Environment Info:

System:
OS: macOS 12.1
CPU: (8) x64 Intel(R) Core(TM) i5-8279U CPU @ 2.40GHz
Binaries:
Node: 16.11.1 - ~/.nvm/versions/node/v16.11.1/bin/node
Yarn: 1.22.17 - ~/.nvm/versions/node/v16.11.1/bin/yarn
npm: 8.0.0 - ~/.nvm/versions/node/v16.11.1/bin/npm
Browsers:
Chrome: 97.0.4692.71
Safari: 15.2
npmPackages:
@storybook/addon-a11y: ^6.4.9 => 6.4.9
@storybook/addon-actions: ^6.4.9 => 6.4.9
@storybook/addon-docs: ^6.4.9 => 6.4.9
@storybook/addon-knobs: ^5.3.21 => 5.3.21
@storybook/addon-viewport: ^6.4.9 => 6.4.9
@storybook/preset-typescript: ^3.0.0 => 3.0.0
@storybook/react: ^6.4.9 => 6.4.9

Additional context
It works if I downgrade the project to react 16.14.0

@joepuzzo
Copy link

I am also getting exact same error when updating to react 17 with storybook

@andrewdoyle19
Copy link

What's the workaround that's marked? Downgrade to react 16.14?

@mohamedMok
Copy link

Hello,
We had the same issue on our storybook (for vue3) using lerna.
We specified in our main package.json the 16.14 version

In one of our packages, a dependency was using react 17 and when lerna detected, it was the version used.

@lurch83 You're right, to fix it we had to force the react version (16.14) in our storybook package.

@shilman I would love to help or contribute to avoiding this type of workaround with Storybook.

@kristi-centinaro
Copy link

I was able to overcome this error by upgrading react AND react-dom to 17.0.2.
I hope this helps others!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants