Here at RabbitMQ HQ we spend quite a lot of time arguing. AtomizeJS is a JavaScript library for writing distributed programs, that run in the browser, without having to write any application specific logic on the server. To use this feature, you must first specify in your manifest.json which websites you want to communicate with using. ) # Sending messages from web pagesĪs with cross-extension messaging, your extension can receive and respond to messages from regular web pages.

Sending a request from a content script looks like this: ( async ( ) => ) You cannot use both a promise and a callback. For backward compatibility, you can alternatively pass a callback as the last argument. To handle the response, use the returned Promise. This lets you send a one-time JSON-serializable message from a content script to the extension, or vice versa. If you only need to send a single message to another part of your extension (and optionally get a response back), use the simplified ndMessage() method or ndMessage() method. That is covered in the cross-extension messages section.

It is also possible to send a message to another extension if you know its ID.

There is a simple API for one-time requests and a more complex API for long-lived connections to exchange multiple messages within shared context. A message can contain any valid JSON object (null, boolean, number, string, array, or object). Either side can listen for messages sent from the other end, and respond on the same channel. For example, an RSS reader extension might use content scripts to detect the presence of an RSS feed on a page, then notify the background page in order to display a page action icon for that page.Ĭommunication between extensions and their content scripts works by using message passing. Since content scripts run in the context of a web page and not the extension, they often need some way of communicating with the rest of the extension.

Web messaging