JarCastingwindow-post-message-proxy
A library used in place of the native window.postMessage, which when used on both the sending and receiving windows allows for nicer asynchronous promise messaging between the windows.
When sending messages using the proxy, it will apply a unique ID to the message, create a deferred object referenced by the ID, and pass the message on to the target window. The target window will also have an instance of the windowPostMessage proxy setup, which will send back messages and preserve the unique ID. The original sending instance then receives the response message with the ID and looks to see if there is a matching id in its cache. If so, it resolves the deferred object with the response.
Documentation
https://microsoft.github.io/window-post-message-proxy
Installation
npm install --save window-post-message-proxy
Basic Usage
// Setup
const iframe = document.getElementById("myFrame");
const windowPostMessageProxy = new WindowPostMessageProxy();
// Send message
const message = {
key: "Value"
};
windowPostMessageProxy.postMessage(iframe.contentWindow, message)
.then(response => {
});
Advanced Customization
Customizing how tracking properties are added to the method
By default, the windowPostMessage proxy will store the tracking properties as an object on the message named windowPostMessageProxy.
This means if you call:
const message = {
key: "Value"
};
windowPostMessageProxy.postMessage(iframe.contentWindow, message);
The message is actually modified before it's sent to become:
{
windowPostMessageProxy: {
id: "ebixvvlbwa3tvtjra4i"
},
key: "Value"
};
If you want to customize how the tracking properties are added to and retrieved from the message, you can pass settings to the constructor in the form of an object with two functions:
export interface IProcessTrackingProperties {
addTrackingProperties<T>(message: T, trackingProperties: ITrackingProperties): T;
getTrackingProperties(message: any): ITrackingProperties;
}
addTrackingProperties takes a message and adds the tracking properties object and returns the message. getTrackingProperties takes a message and extracts the tracking properties.
Example:
const customProcessTrackingProperties = {
addTrackingProperties(message, trackingProperties) {
message.headers = {
'tracking-id': trackingProperties.id
};
return message;
},
getTrackingProperties(message): ITrackingProperties {
return {
id: message.headers['tracking-id']
};
}
};
const windowPostMessageProxy = new WindowPostMessageProxy(customProcessTrackingProperties);
Customizing how messages are detected as error responses.
By default, response messages are considered error messages if they contain an error property.
You can override this behavior by passing an isErrorMessage function at construction time:
export interface IIsErrorMessage {
(message: any): boolean;
}
Example:
function isErrorMessage(message: any) {
return !(200 <= message.status && message.status < 300);
}
const windowPostMessageProxy = new WindowPostMessageProxy({ isErrorMessage });
Logging messages
By default, messages are not logged, but you can override this behavior by passing logMessages: true in the options object.
const windowPostMessageProxy = new WindowPostMessageProxy({ logMessages: true });
This will print out a stringified JSON of each object that is received or sent by the specific instance.
Supplying custom name
Each windowPostMessageProxy gives itself a randomly generated name so you can see which instance is communicating in the log messages. Often times you may want to pass a custom name for the window on which the windowPostMessageProxy instance is running.
You can provided a name by passing name: 'Iframe' in the options object.
const windowPostMessageProxy = new WindowPostMessageProxy({ name: 'Iframe' });
Supress Warning Message about unhandled messages
By default, the window post message proxy will warn you if it receives a message that was not handled, since this is usually an indication of error. However, if you register multiple window message handlers, the message may in fact be handled despite being unknown to the windowPostMessageProxy. In cases like this, this warning no longer applies, so you can disable it by setting suppressWarnings: true:
const windowPostMessageProxy = new WindowPostMessageProxy({ suppressWarnings: true });
