Technology has always been a bridge, but today, it feels more like a mirror. With the rapid rise of AI , we are seeing things enter our lives and leave them at a pace we can barely track. To understand where this is going, we first have to understand how technology actually impacts the core of who we are. The Survivalist vs. The Ego Our minds are biologically wired for one thing: survival . We are designed to handle the worst-case scenario, an ancient instinct gifted to us by nature. We consider ourselves conscious decision-makers, but a critical question remains: Who is really making the call?
Introduction:
Lightning Message Service (LMS) is a powerful communication channel in the Lightning Web Components (LWC) framework that allows you to exchange messages between LWC components, Aura components, and Visualforce pages. It provides a decoupled architecture, enabling components to communicate without having a direct dependency on each other. In this blog post, we will explore how to implement LMS in LWC with a comprehensive working code example.
Prerequisites:
To follow along with this tutorial, you should have a basic understanding of LWC development and have the Salesforce DX CLI installed. Ensure that you have a Salesforce org or scratch org set up for development.
Step 1: Set Up the LWC Component Structure
Create a new LWC component by executing the following command in the command-line interface:
sfdx force:lightning:component:create -n LmsComponent -d force-app/main/default/lwc
Step 2: Define the LMS Message Channel
In your newly created lmsComponent, create a new JavaScript file called lmsChannel.js and define the LMS message channel. This channel will be used for communication between components. Add the following code to lmsChannel.js:
import { LightningElement } from 'lwc';
import { createMessageChannel, releaseMessageChannel } from 'lightning/messageService';
export default class LmsChannel extends LightningElement {
channel = null;
connectedCallback() {
createMessageChannel({ messageChannelName: 'LmsChannel' })
.then((response) => {
this.channel = response;
})
.catch((error) => {
console.error('Error creating LMS message channel', error);
});
}
disconnectedCallback() {
releaseMessageChannel(this.channel)
.then(() => {
this.channel = null;
})
.catch((error) => {
console.error('Error releasing LMS message channel', error);
});
}
}
Step 3: Create a Publisher Component
Create a new JavaScript file called lmsPublisher.js in the lmsComponent folder. This component will publish messages to the LMS channel. Add the following code to lmsPublisher.js:
import { LightningElement } from 'lwc';
import { publish, MessageContext } from 'lightning/messageService';
import LMS_CHANNEL from './lmsChannel';
export default class LmsPublisher extends LightningElement {
message = '';
handleChange(event) {
this.message = event.target.value;
}
handleClick() {
const payload = { value: this.message };
publish(this.context, LMS_CHANNEL, payload);
}
// Get the message context for LMS
context = MessageContext;
// Rest of the component code
}
Step 4: Create a Subscriber Component
Create a new JavaScript file called lmsSubscriber.js in the lmsComponent folder. This component will subscribe to messages published on the LMS channel. Add the following code to lmsSubscriber.js:
import { LightningElement, wire } from 'lwc';
import { subscribe, MessageContext } from 'lightning/messageService';
import LMS_CHANNEL from './lmsChannel';
export default class LmsSubscriber extends LightningElement {
receivedMessage = '';
@wire(MessageContext)
messageContext;
subscription = null;
connectedCallback() {
this.subscribeToChannel();
}
subscribeToChannel() {
if (this.subscription) {
return;
}
this.subscription = subscribe(
this.messageContext,
LMS_CHANNEL,
(message) => {
this.handleMessage(message);
}
);
}
handleMessage(message) {
this.receivedMessage = message ? message.value : '';
}
disconnectedCallback() {
if (this.subscription) {
releaseMessageContext(this.messageContext);
this.subscription = null;
}
}
// Rest of the component code
}
Step 5: Wire Up the Components
In the lmsComponent folder, open the lmsComponent.html file and replace its contents with the following code:
<template>
<div>
<h1>Publisher Component</h1>
<lightning-input type="text" label="Message" onchange={handleChange}></lightning-input>
<lightning-button label="Publish" onclick={handleClick}></lightning-button>
</div>
<div>
<h1>Subscriber Component</h1>
<p>Received Message: {receivedMessage}</p>
</div>
</template>
Step 6: Add the Components to a Lightning Page
In your Salesforce org or scratch org, create a Lightning page where you want to test the LMS components. Add the `lmsComponent` to the Lightning page by using the Lightning App Builder or the Metadata API.
Step 7: Verify the Implementation
Open the Lightning page that contains the lmsComponent. Test the LMS implementation by entering a message in the Publisher Component's input field and clicking the Publish button. The Subscriber Component should receive the published message and display it in the "Received Message" section.
Conclusion:
In this blog post, we explored how to implement Lightning Message Service (LMS) in LWC. By following the step-by-step guide and using the provided code examples, you can create dynamic and decoupled communication between components in your LWC applications. LMS simplifies component interaction and enhances code reusability, making it an invaluable feature for building robust Salesforce applications using LWC.