-
Notifications
You must be signed in to change notification settings - Fork 163
🔧 migrate the developer-extension to wxt #3962
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
base: main
Are you sure you want to change the base?
Conversation
b375739 to
8ec48a9
Compare
Bundles Sizes Evolution
🚀 CPU Performance
🧠 Memory Performance
|
|
✅ Tests 🎉 All green!❄️ No new flaky tests detected 🔗 Commit SHA: ab845f9 | Docs | Datadog PR Page | Was this helpful? Give us feedback! |
f9e1b58 to
749be31
Compare
749be31 to
2d15023
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we clarify why we need this? As we didn't have it before.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We did have it before, just not as a separate file. I linked to MDN docs in the README to clarify a bit the architecture.
Co-authored-by: Ursula Chen <[email protected]>
I removed the warning. I don't think we can remove the dotenv log / tip unfortunately. I'll see if we can avoid building the extension when running |
e4dea2e to
ab845f9
Compare
Excellent, sounds good! |

Motivation
The webpack configuration for the devtools extension is rather tedious to maintain. WXT offers a better DX out of the box, with a single dependency.
We tried going with a basic Vite config file, but it was proven too cumbersome because of the need to use one config per entry point.
Changes
Replace webpack with WXT
Test instructions
In the extension folder, run
yarn devto open a browser with the extension installed.You can also run
yarn buildto build it.Checklist