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
Reading the Chrome Extensions documentation, I understand that they are planning to phase out MV2 in the future.
Have you already considered updating your package to meet the MV3 requirements?
I understand that they are also changing their CSP policies eliminating the use of 'unsafe-eval' from the script-src directive. Could that pose a migration problem for your package?
Since the upgrade is inevitable, I thought it would be wise to adapt to these changes ASAP and start coding future-proof extensions without thinking about what could potentially go obsolete down the road because of a postponed migration.
The text was updated successfully, but these errors were encountered:
Hi @Kocal sorry to pester you for the same question again. I know you already pointed to the #654 comment but after searching for hours I'm still banging my head trying to run your package with service workers in dev/watch mode. I followed the steps from #654 but I still get a generic error - Service worker registration failed.
Is there any way I could run this package with MV3 and service workers in dev mode with auto reload?
I'd appreciate any help or least direction to search further.
Reading the Chrome Extensions documentation, I understand that they are planning to phase out MV2 in the future.
Have you already considered updating your package to meet the MV3 requirements?
I understand that they are also changing their CSP policies eliminating the use of 'unsafe-eval' from the script-src directive. Could that pose a migration problem for your package?
Since the upgrade is inevitable, I thought it would be wise to adapt to these changes ASAP and start coding future-proof extensions without thinking about what could potentially go obsolete down the road because of a postponed migration.
The text was updated successfully, but these errors were encountered: