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.2.0-beta.14] Unknown exception created by Scroller #14214

Closed
matheo opened this issue Mar 12, 2021 · 18 comments
Closed

[6.2.0-beta.14] Unknown exception created by Scroller #14214

matheo opened this issue Mar 12, 2021 · 18 comments

Comments

@matheo
Copy link
Member

matheo commented Mar 12, 2021

Describe the bug

I was trying to see if the @next version had fixed this issue:

image

but instead I got:

image

To Reproduce

I've updated my packages from ~6.1.21 to ~6.2.0-beta.14
Do I need to update something in my webpack config or something?

System

System:
    OS: Linux 5.4 Ubuntu 20.04.2 LTS (Focal Fossa)
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 12.18.3 - ~/.nvm/versions/node/v12.18.3/bin/node
    Yarn: 1.22.5 - /usr/bin/yarn
    npm: 6.14.6 - ~/.nvm/versions/node/v12.18.3/bin/npm
  Browsers:
    Chrome: 89.0.4389.82
    Firefox: 86.0
  npmPackages:
    @storybook/addon-a11y: ~6.2.0-beta.14 => 6.2.0-beta.14 
    @storybook/addon-actions: ~6.2.0-beta.14 => 6.2.0-beta.14 
    @storybook/addon-docs: ~6.2.0-beta.14 => 6.2.0-beta.14 
    @storybook/addon-links: ~6.2.0-beta.14 => 6.2.0-beta.14 
    @storybook/addon-viewport: ~6.2.0-beta.14 => 6.2.0-beta.14 
    @storybook/addons: ~6.2.0-beta.14 => 6.2.0-beta.14 
    @storybook/angular: ~6.2.0-beta.14 => 6.2.0-beta.14

Additional context

I've removed my custom panel and my 6.1 installation seems to not work with 6.2 🤔

@shilman
Copy link
Member

shilman commented Mar 12, 2021

Did you try removing node_modules and/or lockfiles and reinstalling?

@matheo
Copy link
Member Author

matheo commented Mar 12, 2021

@shilman yep, I doubled checked and I did refresh the node_modules when updating it :)

@ayhid
Copy link

ayhid commented Apr 9, 2021

I have the same issue with 6.2.7 :/ @matheo did you solve the problem ?

@matheo
Copy link
Member Author

matheo commented Apr 10, 2021

Nope, I'm still waiting a deep solution :(
cc @shilman

@shilman
Copy link
Member

shilman commented Apr 10, 2021

Do you have a repro repo you can share?

@carlosbaraza
Copy link

I'm getting this error too. It happens intermittently, sometimes when I change the main.js or preview.js it will start appearing. And sometimes it will just work, which makes it quite strange.

Screenshot 2021-04-19 at 21 03 25

@carlosbaraza
Copy link

Not sure if this has fixed it. But I updated react to 17.0.2 (was on 17.0.1) and react-dom, and now it seems to be stable 🤞

@matheo
Copy link
Member Author

matheo commented Apr 19, 2021

Thanks for the tip @carlosbaraza !

@matheo
Copy link
Member Author

matheo commented Apr 19, 2021

Didn't work for my repo 😞
(I see that @storbook/angular relies on react@16.14 but I guess it doesn't affect the manager, dunno)

image

@shilman
Copy link
Member

shilman commented Apr 20, 2021

@matheo that dep is for the manager. we can try updating it in 6.3 and see if that fixes your problem?

@matheo
Copy link
Member Author

matheo commented Apr 20, 2021

yes please @shilman 🙂

@evelynhathaway
Copy link

Data point: We were already on react and react-dom v17, but upgrading to the v6.3.0 storybook beta and downgrading back to stable worked. Possibly it was an issue with our cached manager or node module resolutions.

@matheo
Copy link
Member Author

matheo commented May 28, 2021

@shilman I've upgraded to @storybook/angular@6.3.0-beta.4 and it still uses react-dom@16.14.0 therefore I have no way to confirm that the exception comes from that one, I still have it :(

@gavmck
Copy link

gavmck commented Aug 31, 2021

I had some conflicting versions of react which I'm not sure contributed to this. I ended up having to delete my package-lock.json and node_modules folder and re-run npm install.

The error initially surfaced during a mass upgrade of dependencies to try and bring things up to date.

@matheo
Copy link
Member Author

matheo commented Oct 7, 2021

I finally found a solution while upgrading to Storybook v6.3.9!
To fix my package.json to React v16:

    "react": "16.14.0",
    "react-is": "16.13.1",

@matheo matheo closed this as completed Oct 7, 2021
@ChazUK
Copy link

ChazUK commented Nov 1, 2021

I am also getting this error, I tried using React 17.0.2 and 16.14.0 but still getting the Scroller error.

Environment Info:

System:
OS: macOS 10.15.7
CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
Binaries:
Node: 14.17.0 - /usr/local/bin/node
Yarn: 2.4.3 - ~/.npm-global/bin/yarn
npm: 6.14.13 - /usr/local/bin/npm
Browsers:
Chrome: 94.0.4606.113
Safari: 15.1
npmPackages:
@storybook/addon-actions: ^6.1.15 => 6.3.12
@storybook/addon-backgrounds: ^6.1.15 => 6.3.12
@storybook/addon-controls: ^6.1.15 => 6.3.12
@storybook/addon-docs: ^6.1.15 => 6.3.12
@storybook/addon-jest: ^6.1.15 => 6.3.12
@storybook/addon-knobs: 6.1.15 => 6.1.15
@storybook/addon-viewport: ^6.1.15 => 6.3.12
@storybook/angular: ^6.1.15 => 6.3.12
@storybook/react: ^6.1.15 => 6.3.12

@ChazUK
Copy link

ChazUK commented Nov 1, 2021

Sorry, nuked my node_modules folder and switch to 16.14.0 and it's now working!

@Pringels
Copy link

Pringels commented Nov 4, 2021

I have the same issue. (@storybook/preact: ^6.3.12, Preact 10.5.14)

Tried nuking node_modules and lockfiles but nothing works.

Update: If I remove @storybook/addon-postcss it works again.

Update 2: Adding @storybook/addon-postcss back and switching to v6.4.0-beta.28 fixes the issue.

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

8 participants