Zinn Hub
0
Your Cart
0

At a Glance

Key details about this service to help you decide. Generated by Zinn Hub, not the seller.

Languages Supported

JavaScript & TypeScript
Works with both JS and TS codebases - no need to convert your project before sending it over.

Migration Type

Manifest V2 → V3
Covers the full MV3 change set: background page to service worker, webRequest to declarativeNetRequest, and removal of remote code execution.

Delivery Method

Your own repo, no store access needed
You keep full control - the vendor never touches your store listing or developer account. You upload the final build yourself.

Best For

Live extensions with real users
Designed to preserve existing behaviour - only what the fix or MV3 requires changes, minimising disruption to current users.

What You'll Receive

Formats:
Written Report
Custom Code
Delivery Method:
Order Manager

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

✓
Vetted Professional
Every Zinner is reviewed and approved before joining the platform.
✓
Quality Work Guaranteed
All services are backed by our quality assurance commitment.
✓
Secure Payment
Your payment is protected until you approve the delivered work.

Compare Packages

ФункцияStarterStandardAdvanced
Delivery Time2 days4 days10 days
Revisions123
Scope1 problem found and fixedUp to 3 problems, or a V3 moveManifest V3, up to 5 screens
Bug investigation✓✓✓
Fix documentation✓✓✓
Detailed code comments✕✓✓

Service Details

Service Type
Standard
Zinner Type
Freelancer
Availability
Weekdays
Seller's Country
Kazakhstan
Languages Accepted
English
Russian
NDA available
Yes
Project Sizes Handled
Small To Medium
Response time
Within 12 hours
Years of Experience
10+

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

Categories

Zinner Policies

I Will Fix Your Chrome Extension Or Move It To Manifest V3 2 &Raquo; Zinn Hub

Only logged in customers who have purchased this product may leave a review.

Options & Order

Get the Zinn Hub App

Notifications · Faster access · Full-screen

Tap Share in your browser

➜ Then tap "Add to Home Screen"