𝗨𝗻𝗽𝗮𝗰𝗸𝗶𝗻𝗴 𝗠𝗮𝗻𝗶𝗳𝗲𝘀𝘁 𝗩𝟯

𝗨𝗻𝗽𝗮𝗰𝗸𝗶𝗻𝗴 𝗠𝗮𝗻𝗶𝗳𝗲𝘀𝘁 𝗩𝟯

Google is replacing Manifest V2 with Manifest V3. This change changes how Chrome extensions work.

A manifest is a file that tells the browser how an extension runs. Manifest V3 changes the rules to focus on privacy, security, and speed.

Major Changes

• Service Workers replace background pages. These work in short bursts instead of running constantly.
• declarativeNetRequest replaces webRequest. Extensions can no longer intercept data in real time. They must give Chrome a list of rules to block things.
• No remote code. Extensions must include all code inside the package. You cannot load code from an external server.
• Promise-based APIs. This makes coding faster and more modern.

The Challenges for Developers

Migrating is difficult. It requires a complete redesign.

• You must move from background pages to stateless service workers.
• You cannot access the window or document in the background.
• You must use Offscreen Documents for tasks like audio or DOM parsing.

New Limitations

• Rule limits. Google limits the number of rules an extension can use. This makes ad-blockers less effective.
• Statelessness. Service workers stop running after a few minutes of inactivity. You must save data to storage to keep it.
• Slow updates. Since you cannot use remote code, you must submit a new extension to the Web Store to update blocklists.

The Pros and Cons

Pros

• Better security. Malicious code cannot run after the initial review.
• Better privacy. Extensions see less of your data.
• Better performance. Service workers use less memory and battery.

Cons

• Weaker ad-blockers. Advanced filtering is now harder to build.
• Developer friction. The new rules create more work and less freedom.
• Less user control. Power users have fewer ways to manage web traffic.

Manifest V3 makes the browser safer and faster for most people. It also limits the tools available to power users.

Source: https://dev.to/tene/unpacking-manifest-v3-chromes-big-extension-shakeup-15n6