# reactor-bridge

**Repository Path**: mirrors_adobe/reactor-bridge

## Basic Information

- **Project Name**: reactor-bridge
- **Description**: Communication API between the Tags UI (Lens) and extension views.
- **Primary Language**: Unknown
- **License**: Apache-2.0
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2020-09-24
- **Last Updated**: 2026-03-21

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# Adobe Experience Platform Tags Extension Bridge

[![npm (scoped with tag)](https://img.shields.io/npm/v/@adobe/reactor-bridge.svg?style=flat)](https://www.npmjs.com/package/@adobe/reactor-bridge)

Adobe Experience Platform Tags is a next-generation tag management solution enabling simplified deployment of marketing technologies. For more information regarding Experience Platform Tags, please visit our [product website](http://www.adobe.com/enterprise/cloud-platform/launch.html).

When a Tags user configures extensions, rules, and data elements within the Tags UI, the UI presents an extension's view within an iframe. This project provides the communication layer between the Tags UI and extension views for storage and retrieval of settings, validation, etc. It does so by exposing a simplified, abstracted API while leveraging the native `postMessage` browser API under the hood.

For more information about developing an extension for Experience Platform Tags, please visit our [extension development guide](https://experienceleague.adobe.com/docs/experience-platform/tags/extension-dev/overview.html).

## Usage

The Tags UI consumes the bridge via the `@adobe/reactor-bridge` npm package while extension views consume the bridge by loading a CDN-hosted script as described in the [extension development guide](https://experienceleague.adobe.com/docs/experience-platform/tags/extension-dev/overview.html).

The communication layer consists three different pieces:

* **Parent (lib/parent.js):** This is the portion of the communication layer that the Tags UI uses. The Tags UI uses this by importing it directly:

  `import { loadIframe } from '@adobe/reactor-bridge';`
  
  The arguments, return value, and behavior of `loadIframe` can be found within the code documentation in `parent.js`.

* **Child (dist/extensionbridge-child.js):** This is the portion of the communication layer that extension views use, though extension views don't load it directly (see Child Loader). This file is hosted by the Tags UI which means it may be different based on the environment. This is important since it needs to be compatible with the Parent that is being used by the Tags UI in the same environment.
* **Child Loader (dist/extensionbridge.js):** This loads Child. Child Loader will be loaded by extensions via a `script` tag. Extensions will always load the same Child Loader regardless of the environment they are running in. Child Loader then loads the environment-specific Child.

## Contributing

Contributions are welcomed! Read the [Contributing Guide](CONTRIBUTING.md) for more information.

To get started:

1. Install [node.js](https://nodejs.org/).
3. Clone the repository.
4. After navigating into the project directory, install project dependencies by running `npm install`.

### Scripts

To run tests a single time, run the following command:

`npm run test`

To run tests continually while developing, run the following command:

`npm run test:watch`

To run a sandbox where you can manually test your changes (manipulate the sandbox directory as desired), run the following command:

`npm run sandbox`

To create a build, run the following command:

`npm run build`

## Browser Support

The extension bridge supports the following browsers:

* Chrome (latest)
* Safari (latest)
* Firefox (latest)
* Edge (latest)
 
## Licensing

This project is licensed under the Apache V2 License. See [LICENSE](LICENSE) for more information.