Eduardo Aparicio Cardenes

Thanks for sharing for additional coverage. This is helpful because it validates that we are experiencing the same issues.

@0xBigBoss, I saw you close the PR. How did it go with your approach to support Manifest V3? Did you see any issues that drove you to close the PR?

@0xBigBoss Makes sense, I am glad to hear it is working fine. I have had a similar experience with my solution of continuously broadcasting state changes to all content scripts...

Do you have any update on the support for React 18? I found even a [PR](https://github.com/react-dates/react-dates/pull/2235) was to upgrade this, but it's closed

From what I read across #2105 #1748, it comes across like there needs to be more interest in maintaining up to date the project. Could you confirm if this package...

> The package remains maintained, but that doesnt mean I've had time to work on react 17 and 18 support. > > Companies donating employee time and/or funds to cover...

Thanks, @bradyshutt. I will give it a try and share its outcome 🤞

We are experiencing the same problem, affecting our production users on version `google-closure-compiler: 20240317.0.0.` as it was working in our previous version `20180805.0.0` Why is this flag no longer working?...