Your extension worked last month and it doesn't now. Chrome shipped an update, the site underneath changed its markup, or it still runs on Manifest V2 and the store won't take it any more. I repair those, in JavaScript and TypeScript.
I Will fix your Chrome extension or move it to Manifest V3
1 reproducible problem found, fixed and explained; source in your repository.
- 1 problem found and fixed
- Bug investigation
- Fix documentation
Up to 3 problems, or a one-screen extension moved to Manifest V3, plus summary.
- Up to 3 problems, or a V3 move
- Bug investigation
- Fix documentation
- Detailed code comments
Up to 5 screens moved to Manifest V3, a written summary, other problems listed.
- Manifest V3, up to 5 screens
- Bug investigation
- Fix documentation
- Detailed code comments
Request a Custom Offer
Log In to Request a Custom Offer
Create a free account or log in to request a personalised offer from this Zinner.
Log In / RegisterAsk a Pre-Sale Question
Log In to Ask a Question
To reduce platform spam, pre-sale messages can only be sent by logged-in users.
Create a free account or log in to message this Zinner directly.
Log In / RegisterAt a Glance
Key details about this service to help you decide. Generated by Zinn Hub, not the seller.
Value Position
Languages Supported
Migration Type
Delivery Method
Best For
What You'll Receive
Full Description
Aimed at companies and solo developers whose extension already has users counting on it. You get the same extension back, changed only where the fix or Manifest V3 requires it, so those users notice as little change as possible.
Send me the source or the store link and what goes wrong. You get back a build you load in developer mode and click through yourself, the cause written out in plain words, and the source in your own repository.
Starter is one reproducible problem: a popup that opens empty, a permission error, a content script that no longer matches the page. Standard takes up to 3 of those, or moves a single-screen extension to Manifest V3. Advanced migrates an extension of up to 5 screens and lists the other problems I found on the way. A second broken thing is a second item: the add-on, or a new order.
Building a new extension is my other project. This one starts from code that already exists.
What I turn down, and I say it before the project rather than after: anything that needs someone else's login, harvests personal data, or works a service against its own rules.
No calls. Everything in writing, including what was actually broken.
Steps for completing your project
1. Reproduce it, or unpack it - I load your extension in developer mode and reproduce the problem from your steps, or unpack the store build if the source is gone. If it does not reproduce, you hear it the same day.
2. The cause, in writing - What actually broke: a Chrome API that changed, a page whose markup moved, a Manifest V2 feature the store no longer accepts. Plain words, before the fix.
3. Fix, or migrate - The fix, or the Manifest V3 move: background page to service worker, request blocking to declarative rules, remote code brought inside. Each change with its reason.
4. Clean-profile test and a build for you - The fixed build tested on a clean profile, then handed to you to load in developer mode and click through on your own machine before you approve.
5. Handover in your repository - Source in your repository, the written summary on Standard and Advanced, and a note on what to upload to the store from your own account.
Zinner Quality Guarantee
Every Zinner is reviewed and approved before joining the platform.
All services are backed by our quality assurance commitment.
Your payment is protected until you approve the delivered work.
Compare Packages
| Функция | Starter | Standard | Advanced |
|---|---|---|---|
| Delivery Time | 2 days | 4 days | 10 days |
| Revisions | 1 | 2 | 3 |
| Scope | 1 problem found and fixed | Up to 3 problems, or a V3 move | Manifest V3, up to 5 screens |
| Bug investigation | ✓ | ✓ | ✓ |
| Fix documentation | ✓ | ✓ | ✓ |
| Detailed code comments | ✕ | ✓ | ✓ |
Service Details
Frequently Asked Questions
Yes, that is the usual reason people come here. Send the extension and what you see now, and I will tell you the cause and which tier covers it before you buy.
It is not a rename. The background page becomes a service worker that stops and restarts, blocking webRequest gives way to declarativeNetRequest rules, and code can no longer be loaded from a server. Whatever used those gets rewritten, not adjusted.
Often yes: a published extension can be unpacked. If what comes out is minified or obfuscated I tell you before you buy, and say straight whether repairing it beats rebuilding it.
Nothing I do touches the store listing. I work on a copy you load in developer mode, and the new build goes up when you upload it yourself, from your own developer account.
Customer Reviews
See what our customers say about this Zinn







