The Power of Signals for Scalable Application Development

Overview

React, a JavaScript library for building user interfaces has become immensely popular for its declarative and component-based approach. While React provides a robust state management system, there are scenarios where you might need to implement a more granular and efficient communication mechanism between components. In this blog post, we’ll explore the concept of signals in React, how they differ from traditional state management, and how to implement them effectively.

Pioneers in Cloud Consulting & Migration Services

Reduced infrastructural costs
Accelerated application deployment

Get Started

Understanding Signals

Signals, in the context of React, refer to a mechanism for communication between different parts of your application. Unlike traditional state management, signals allow you to broadcast messages and have multiple components subscribe to those messages without direct parent-child relationships.

This makes signals a powerful tool for handling communication in a more decoupled and scalable way.

The Need for Signals

Consider a scenario with a complex React application with multiple components scattered across the hierarchy. Traditional state management might involve passing props through several layers of components or lifting the state up to a common ancestor. However, this can lead to a convoluted and less maintainable codebase.

Signals provide a cleaner solution by allowing components to communicate without knowing about each other. This can be particularly useful in global events, user authentication changes, or situations where multiple components must respond to a shared event.

Implementing Signals with a Library

You can leverage existing libraries like mitt or nanoevents to implement signals in React. These libraries provide a lightweight and easy-to-use API for emitting and listening to events. Let’s explore a basic example using mitt:

// Install mitt using npm or yarn: npm install mitt
import mitt from 'mitt';
// Create a global emitter
const emitter = mitt();
// Component A
function ComponentA() {
  // Subscribe to the 'customEvent'
  useEffect(() => {
    const handler = () => {
      // Handle the event
      console.log('Component A received the event');
    };
    emitter.on('customEvent', handler);
    // Unsubscribe on component unmount
    return () => {
      emitter.off('customEvent', handler);
    };
  }, []);
  return <div>Component A</div>;
}
 
// Component B
function ComponentB() {
  // Trigger the 'customEvent' when the component mounts
  useEffect(() => {
    emitter.emit('customEvent');
  }, []);
  return <div>Component B</div>;
}

// Install mitt using npm or yarn: npm install mitt

import mitt from 'mitt';

// Create a global emitter

const emitter = mitt();

// Component A

function ComponentA() {

// Subscribe to the 'customEvent'

useEffect(() => {

const handler = () => {

// Handle the event

console.log('Component A received the event');

};

emitter.on('customEvent', handler);

// Unsubscribe on component unmount

return () => {

emitter.off('customEvent', handler);

};

}, []);

return <div>Component A</div>;

}

// Component B

function ComponentB() {

// Trigger the 'customEvent' when the component mounts

useEffect(() => {

emitter.emit('customEvent');

}, []);

return <div>Component B</div>;

}

In this example, ComponentA subscribes to the ‘customEvent’, and ComponentB triggers this event when it mounts. The components are decoupled, and neither needs to know about the existence of the other. This makes the code more maintainable and scalable.

Building a Custom Signal System

You can implement a simple signal system using React’s context and hooks if you prefer a custom solution without relying on external libraries. Let’s create a custom signal hook:

import React, { createContext, useContext, useEffect } from 'react';
// Create a context for the signal
const SignalContext = createContext();
// Custom hook to access the signal emitter
export function useSignal() {
  return useContext(SignalContext);
}
// SignalProvider component to wrap your app
export function SignalProvider({ children }) {
  const emitter = mitt();
 
  // Clean up the emitter on unmount
  useEffect(() => {
    return () => {
      emitter.all.clear();
    };
  }, []);
  return (
    <SignalContext.Provider value={emitter}>
      {children}
    </SignalContext.Provider>
  );
}

import React, { createContext, useContext, useEffect } from 'react';

// Create a context for the signal

const SignalContext = createContext();

// Custom hook to access the signal emitter

export function useSignal() {

return useContext(SignalContext);

}

// SignalProvider component to wrap your app

export function SignalProvider({ children }) {

const emitter = mitt();

// Clean up the emitter on unmount

useEffect(() => {

return () => {

emitter.all.clear();

};

}, []);

return (

<SignalContext.Provider value={emitter}>

{children}

</SignalContext.Provider>

);

}

Now, you can wrap your entire application with the SignalProvider:

// App component
import { SignalProvider } from './SignalProvider';
import ComponentA from './ComponentA';
import ComponentB from './ComponentB';
function App() {
  return (
    <SignalProvider>
      <div>
        <ComponentA />
        <ComponentB />
      </div>
    </SignalProvider>
  );
}
export default App;

// App component

import { SignalProvider } from './SignalProvider';

import ComponentA from './ComponentA';

import ComponentB from './ComponentB';

function App() {

return (

<div>

</div>

</SignalProvider>

);

}

export default App;

Then, components can use the useSignal hook to subscribe and emit events:

// ComponentA.js
import React, { useEffect } from 'react';
import { useSignal } from './SignalProvider';
function ComponentA() {
  const emitter = useSignal();
  useEffect(() => {
    const handler = () => {
      console.log('Component A received the event');
    };
emitter.on('customEvent', handler);
    return () => {
      emitter.off('customEvent', handler);
    };
  }, [emitter]);
  return <div>Component A</div>;
}
export default ComponentA;


// ComponentB.js
import React, { useEffect } from 'react';
import { useSignal } from './SignalProvider';
function ComponentB() {
  const emitter = useSignal();
  useEffect(() => {
    emitter.emit('customEvent');
  }, [emitter]);
  return <div>Component B</div>;
}
export default ComponentB;

// ComponentA.js

import React, { useEffect } from 'react';

import { useSignal } from './SignalProvider';

function ComponentA() {

const emitter = useSignal();

useEffect(() => {

const handler = () => {

console.log('Component A received the event');

};

emitter.on('customEvent', handler);

return () => {

emitter.off('customEvent', handler);

};

}, [emitter]);

return <div>Component A</div>;

}

export default ComponentA;

// ComponentB.js

import React, { useEffect } from 'react';

import { useSignal } from './SignalProvider';

function ComponentB() {

const emitter = useSignal();

useEffect(() => {

emitter.emit('customEvent');

}, [emitter]);

return <div>Component B</div>;

}

export default ComponentB;

Benefits of Signal Use

Decoupling Components: By allowing you to separate components, signals improve the modularity and maintainability of your code.
Global Communication: Components at different levels of the hierarchy can communicate with each other without having to pass props through intermediate layers thanks to signals, which offer a global communication mechanism.
Scalability: The signal system can expand with your application as it grows. Without significantly altering the current code, you can add new components that introduce new signals or subscribe to existing ones.
Cleaner Code: Your code becomes cleaner and more focused on the logic of individual components by eschewing intricate prop-drilling and reliance on a centralized state management library.

Conclusion

This blog post has discussed React’s signal concept and its advantages for controlling component communication. A more modular, scalable, and maintainable codebase can result from integrating signals into your application, whether you use a specific library like mitt or create a custom signal system using React context and hooks. You’ll find that managing events and updates in your React apps can be done flexibly as you learn to use signals.

Drop a query if you have any questions regarding Signals in React and we will get back to you quickly.

Making IT Networks Enterprise-ready – Cloud Management Services

Accelerated cloud migration
End-to-end view of the cloud environment

Get Started

About CloudThat

CloudThat is a leading provider of Cloud Training and Consulting services with a global presence in India, the USA, Asia, Europe, and Africa. Specializing in AWS, Microsoft Azure, GCP, VMware, Databricks, and more, the company serves mid-market and enterprise clients, offering comprehensive expertise in Cloud Migration, Data Platforms, DevOps, IoT, AI/ML, and more.

CloudThat is recognized as a top-tier partner with AWS and Microsoft, including the prestigious ‘Think Big’ partner award from AWS and the Microsoft Superstars FY 2023 award in Asia & India. Having trained 650k+ professionals in 500+ cloud certifications and completed 300+ consulting projects globally, CloudThat is an official AWS Advanced Consulting Partner, AWS Training Partner, AWS Migration Partner, AWS Data and Analytics Partner, AWS DevOps Competency Partner, Amazon QuickSight Service Delivery Partner, Amazon EKS Service Delivery Partner, Microsoft Gold Partner, AWS Microsoft Workload Partners, Amazon EC2 Service Delivery Partner, and many more.

To get started, go through our Consultancy page and Managed Services Package, CloudThat’s offerings.

FAQs

1. What are signals in the context of React?

ANS: – Signals in React typically refer to events or triggers that indicate a change in state or data. This can include user interactions, API responses, or other asynchronous operations that impact the application.

2. How do signals differ from traditional event handling in React?

ANS: – While traditional event handling in React involves synthetic events, signals might encompass a broader range of triggers, including custom events, state changes, or even global events managed by state management libraries.