How Can I Keep a Chrome Extension's Service Worker Persistent?

Persistent Service Worker in Chrome Extension

Despite being transient by nature, it's possible to maintain a persistent Service Worker (SW) in a Chrome extension. This can be crucial for intercepting and interacting with data in specific requests.

Known Problems:

• Timed-Out SW: By default, SWs terminate after 5 minutes of inactivity or after 30 seconds without any activities.

Workarounds:

Bug Exploit (Chrome 110 )

Continuously calling chrome API prolongs the SW lifetime. This bug is treated as a feature and is likely to stay.

Offscreen API (Chrome 109 )

Offscreen documents receive messages, keeping the SW active for an extended period. This solution currently has no apparent lifespan limitations, though it may change.

nativeMessaging API (Chrome 105 )

Connect the SW to a nativeMessaging host. The SW remains active as long as the connection persists.

WebSocket API (Chrome 116 )

Pinging a WebSocket every 25 seconds or less ensures the SW stays active.

Chrome Messaging API

Exchange messages between a persistent background page and the SW to keep it alive.

Dedicated Tab

Open a dedicated tab that serves as a visible background page, eliminating the SW's transient nature.

Caution:

• Enable keep-alive only during critical tasks to avoid unnecessary memory usage.
• Store and restore the SW's state in storage to prevent data loss during crashes.
• Avoid persisting the SW solely for state management; it's only recommended for performance optimization.

The above is the detailed content of How Can I Keep a Chrome Extension's Service Worker Persistent?. For more information, please follow other related articles on the PHP Chinese website!