[x] Add Svelte support and convert the panel UI to Svelte
[x] Add eslint support with a linting check run in a GH action
[x] Add TypeScript support
[x] Add prettier config to support the Svelte VSCode plugin
[x] Update homepage_url in manifests
[x] Remove funding boilerplate
[x] Temporarily disable GH release action (we can bring it back when we are ready to release)
Note that it was necessary to upgrade to Manifest V3 to properly test the build across browser targets. The Manifest V3 changes were primarily adding support for service workers and non-persistent background scripts.
The counter boilerplate was also removed because we probably won't need communication in the devtools panel -> background -> content script direction.
Link to issue
Closes #5.
Closes #6.
Type of change
[x] New feature (non-breaking change that adds functionality)
[x] Refactor (non-breaking change that updates existing functionality)
Test plan (required)
Build the project and load it into Chrome (chrome://extensions) and Firefox (about:debugging > This Firefox). Select the Webnative devtools panel in the devtools and select "Start Tracking" to track mouse movement in the page.
In Chrome, leave the page for five minutes to let the service worker deactivate. Then mouse over the page and the service worker should be reactivated as a result of messages sent through the content script.
In Firefox, terminate the background script in about:debugging. The mouse over the page and it should reactivate. Note that in Firefox you must grant the "Access your data for all websites" for the extension in about:addons.
Description
The PR implements the following features:
vitebuild with Chome and Firefox targetseslintsupport with a linting check run in a GH actionprettierconfig to support the Svelte VSCode pluginhomepage_urlin manifestsNote that it was necessary to upgrade to Manifest V3 to properly test the build across browser targets. The Manifest V3 changes were primarily adding support for service workers and non-persistent background scripts.
The counter boilerplate was also removed because we probably won't need communication in the
devtools panel -> background -> content scriptdirection.Link to issue
Closes #5. Closes #6.
Type of change
Test plan (required)
Build the project and load it into Chrome (
chrome://extensions) and Firefox (about:debugging> This Firefox). Select the Webnative devtools panel in the devtools and select "Start Tracking" to track mouse movement in the page.In Chrome, leave the page for five minutes to let the service worker deactivate. Then mouse over the page and the service worker should be reactivated as a result of messages sent through the content script.
In Firefox, terminate the background script in
about:debugging. The mouse over the page and it should reactivate. Note that in Firefox you must grant the "Access your data for all websites" for the extension inabout:addons.Screenshots/Screencaps