[Bug] - Admin page dropdowns crashed the page

[Bokitza]

Bug report

Required System information

• Node.js version:16.0.0
• NPM version:
• Strapi version: 4.5.2
• Database: PG
• Operating system: Linux

Describe the bug

dropdowns in the admin panel crashes the page with an error

Steps to reproduce the behavior

1. Go to a random Select element
2. Click on it
3. page goes white
4. See error

Expected behavior

Should open the select like in previous versions

Screenshots

in the content manager - Clicking on "item" dropdown

Error

in the wysiwig editor:

Error

[fabio-nettis]

Duplicate of #14993

[joshuaellis]

Hey @Bokitza, are you able to delete the build .cache and rebuild the admin panel to see if this issue goes away? We can see a visual bug in your panel that should also have been fixed by the 4.5.2 release.

[fabio-nettis]

@joshuaellis I can confirm that deleting the .cache, deleting node-modules and re-building the application does indeed not fix the issue. Still persistent in latest version.

[joshuaellis]

@joshuaellis I can confirm that deleting the .cache, deleting node-modules and re-building the application does indeed not fix the issue. Still persistent in latest version.

Then please provide a minimal reproduction of the issue, unfortunately I currently can't reproduce this. Thank you 😊

[Bokitza]

The error stopped after - upgrading to 4.5.3 using npm i - deleting DIST and BUILD folders - running npm run strapi develop thanks all!

…

On Fri, Dec 9, 2022 at 9:08 PM Josh ***@***.***> wrote: @joshuaellis <https://github.com/joshuaellis> I can confirm that deleting the .cache, deleting node-modules and re-building the application does indeed *not* fix the issue. Still persistent in latest version. Then please provide a minimal reproduction of the issue, unfortunately I currently can't reproduce this. Thank you 😊 — Reply to this email directly, view it on GitHub <#15045 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AN3UDNXVIXDELCLRPTPGV33WMN7R7ANCNFSM6AAAAAASPW3LGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- בברכה יואב שגי 0549732436

[joshuaellis]

I ran into this issue today, but found deleting the yarn.lock worked, it looks like an upstream dependency had a custom polyfill that interfered with our minifier, but like I said, removing yarn.lock worked in resolving that issue, this left no visible issues. I'd advise everyone to do the same and see if the error persists.