Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrating to Manifest v3 #22

Open
Mikescops opened this issue Apr 20, 2021 · 1 comment
Open

Migrating to Manifest v3 #22

Mikescops opened this issue Apr 20, 2021 · 1 comment

Comments

@Mikescops
Copy link
Contributor

Hello,

First of all, thanks for this great tool, I use it a lot to kickstart some small projects.

Soon we will all be forced to migrate to manifest v3 so I'm looking into what are the steps needed to still be using neutrino-webextension and hopefully have a smooth transition.

The migration is described by Google here.

The most impacting change is the migration from the background page to a service worker, as described here.

Here are a few extension samples : chrome-extension project

Let me try to sum up the changes in the manifest (I might miss some things):

{
  "background": {
    "scripts": [
      "assets/browser-polyfill.min.js",
      "assets/runtime.d8dd73ab.js",
      "assets/1.7fa210ac.js",
      "assets/background.afd2ca50.js"
    ],
    "persistent": true
  },
  "browser_action": {
    "default_popup": "popup.html"
  },
  "manifest_version": 2
}

becomes

{
  "background": {
    "service_worker": "assets/worker.js",
  },
  "action": {
    "default_popup": "popup.html"
  },
  "manifest_version": 3
}

The entire checklist is available here.

I'll try to have this working and make a PR if possible.

@Mikescops
Copy link
Contributor Author

The main issue being having all the current scripts into one service worker file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant