Migrate to WXT Framework with TypeScript #7
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Convert JavaScript to TypeScript - Set up WXT project structure with entrypoints - Migrate background, content, popup, and options scripts - Create utility library with TypeScript types - Remove licensing integration - Include 'Hide on mouseover' feature from PR #4 - Fix locale files JSON format - Add cross-browser compatibility with webextension-polyfill Co-Authored-By: devin.ko.lab@michielroos.com <michiel@michielroos.com>
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Co-Authored-By: devin.ko.lab@michielroos.com <michiel@michielroos.com>
- Add getHeadersForTab message handler in background script - Implement displayHeaders function with proper panel rendering - Add missing utility functions from original library.js - Fix TypeScript type errors in library functions Co-Authored-By: devin.ko.lab@michielroos.com <michiel@michielroos.com>
- Update runtime.onMessage.addListener to use sendResponse and return true for async responses - Add better error logging in popup's displayHeaders function - Fix TypeErrors with 'i.action is undefined' in background script Co-Authored-By: devin.ko.lab@michielroos.com <michiel@michielroos.com>
- Use correct container ID from library.ts for popup display - Add error handling for browser.action calls in background script - Ensure proper message passing between background and popup Co-Authored-By: devin.ko.lab@michielroos.com <michiel@michielroos.com>
- Replace localStorage with browser.storage.local in pruneHeaderStore - Replace document.createElement with URL API in onSendHeaders - Fix popup container targeting to use both main container and result div Co-Authored-By: devin.ko.lab@michielroos.com <michiel@michielroos.com>
…ssion - Add missing defineBackground import from WXT utils - Add webRequestBlocking permission for header interception - Resolve HTTP header capture and display issues Co-Authored-By: devin.ko.lab@michielroos.com <michiel@michielroos.com>
Author
|
Closing due to inactivity for more than 7 days. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
HTTP Header Spy Migration to WXT - Fixed HTTP Header Capture
I've fixed the HTTP header capture and display issues in the WXT migration:
Fixed Issues:
defineBackgroundimport from WXT utils in background scriptwebRequestBlockingpermission to wxt.config.ts for header interceptionTechnical Details:
defineBackgroundimport, which prevented the webRequest listeners from being registeredTesting:
The extension now builds successfully with WXT and should properly capture and display HTTP headers in the popup. To test the extension:
Load the extension in your browser:
.output/chrome-mv3directory.output/chrome-mv3directoryVisit a website and click the extension icon to verify HTTP headers are displayed with proper styling
All changes have been pushed to the PR: #7