search

jquense / react-widgets

Polished, feature rich, accessible form inputs built with React
http://jquense.github.io/react-widgets/
MIT License
2.34k stars 393 forks source link

Getting "SlideDownTransition.js:61 Uncaught TypeError: Cannot read property 'style' of null" all of a sudden #1069

Open lslee714 opened 3 years ago

lslee714 commented 3 years ago

Hello,

Out of no where today, I started getting this error when trying to open a DropdownList widget. My package.json shows

I've tried upgrading my libraries but that just gave me other errors (likely due to breaking changes from the upgrade).

Any ideas?

Thank you and please let me know if I need to add more information

jquense commented 3 years ago

are you sure those are the resolved versions? I don't know why it would stop out of the blue, we've not pushed any new versions to v4

lslee714 commented 3 years ago

@jquense Thanks for responding so quickly. Yeah I am very confused also on why it just started happening. Will investigate more regarding the versions and report back.

lslee714 commented 3 years ago

@jquense just an update for you, I specified the installed package to match it exactly (i.e. yarn upgrade react-widgets@4.4.11) and now every thing is working again. FWIW, when I looked at what was installed with the ^4.4.11 version, it showed:

Not sure if that helps you or not. Feel free to close this if you believe this is a non-issue.

jquense commented 3 years ago

hmm i'm not sure. sounds like maybe a weird yarn thing. glad it's working. will leave open for now, in case it pops up again

lslee714 commented 3 years ago

Hey @jquense another update for ya.

So I was sort of wrong yesterday when I said it worked again. It did in our main trunk when I got the exact version, but still had the issue in our feature branch.

Naturally this led me to believe it was something in the changes of the branch, so I commented a bunch of the stuff done on the branch to no avail.

Then I went to messing around with versions again of this library but also other react things, still no luck.

Finally I tried using npm instead of yarn and voila, the functionality came back!

Do you have any suggestions as to how I should proceed given this info? Switching everything over to npm is doable obviously, but I'd prefer if there was something more straightforward I could look at and still use yarn.