You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm building a Chrome Extension with manifest v3, bundled with ejected CRA and custom webpack config.
Whenever I install it, both unpacked or from the store, some other extensions as Adblock and Http Everywhere crash, and my extension fails to initialize. I found out that my issue was related to @extend-chrome/storage import, so I removed it and used chrome.storage api with no external dependencies.
I'm sorry but I have not time to create a minimal reproduction right now, since I'm full making an official release of the extension I'm working on.
My thoughts are, maybe it's related to the way manifest v3 works now with service workers, or something creates conflict with the use of rxjs and/or chrome-promise.
Don' t worry about to or not to accept the issue since it's not well compiled, I'm just writing to you for the sake of your own library that was easy to use for me. Bye
How do we reproduce?
Expected behavior
Actual behavior
Screenshots
Please complete the following information:
Library Version:
Operating System:
Browser:
Node Version:
Additional context
The text was updated successfully, but these errors were encountered:
jacksteamdev
changed the title
Conflict with other extensions
Conflict with other extensions in Manifest V3
May 25, 2021
Google search terms
Describe the bug
I'm building a Chrome Extension with manifest v3, bundled with ejected CRA and custom webpack config.
Whenever I install it, both unpacked or from the store, some other extensions as Adblock and Http Everywhere crash, and my extension fails to initialize. I found out that my issue was related to @extend-chrome/storage import, so I removed it and used chrome.storage api with no external dependencies.
I'm sorry but I have not time to create a minimal reproduction right now, since I'm full making an official release of the extension I'm working on.
My thoughts are, maybe it's related to the way manifest v3 works now with service workers, or something creates conflict with the use of rxjs and/or chrome-promise.
Don' t worry about to or not to accept the issue since it's not well compiled, I'm just writing to you for the sake of your own library that was easy to use for me. Bye
How do we reproduce?
Expected behavior
Actual behavior
Screenshots
Please complete the following information:
Additional context
The text was updated successfully, but these errors were encountered: