Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
react-broadcast
Advanced tools
Reliably communicate state changes to deeply nested React elements
react-broadcast
provides a reliable way for React components to propagate state changes to their descendants deep in the component hierarchy, bypassing intermediaries who return false
from shouldComponentUpdate
.
It was originally built to solve issues that arose from using react-router
together with react-redux
. The router needed a safe way to communicate state changes to <Link>
s deep in the component hierarchy, but react-redux
relies on shouldComponentUpdate
for performance. react-broadcast
allows the router to work seamlessly with Redux and any other component that uses shouldComponentUpdate
.
Please note: As with anything that uses context, this library is experimental. It may cease working in some future version of React. For now, it's a practical workaround for the router. If we discover some better way to do things in the future, rest assured we'll do our best to share what we learn.
$ npm install --save react-broadcast
Then, use as you would anything else:
// using ES6 modules
import { createContext } from "react-broadcast";
// using CommonJS modules
var createContext = require("react-broadcast").createContext;
The UMD build is also available on unpkg:
<script src="https://unpkg.com/react-broadcast/umd/react-broadcast.min.js"></script>
You can find the library on window.ReactBroadcast
.
The following is a contrived example, but illustrates the basic functionality we're after:
import React from "react";
import { createContext } from "react-broadcast";
const users = [{ name: "Michael Jackson" }, { name: "Ryan Florence" }];
const { Provider, Consumer } = createContext(users[0]);
class UpdateBlocker extends React.Component {
shouldComponentUpdate() {
// This is how you indicate to React's reconciler that you don't
// need to be updated. It's a great way to boost performance when
// you're sure (based on your props and state) that your render
// output will not change, but it makes it difficult for libraries
// to communicate changes down the hierarchy that you don't really
// know anything about.
return false;
}
render() {
return this.props.children;
}
}
class App extends React.Component {
state = {
currentUser: Provider.defaultValue
};
componentDidMount() {
// Randomly change the current user every 2 seconds.
setInterval(() => {
const index = Math.floor(Math.random() * users.length);
this.setState({ currentUser: users[index] });
}, 2000);
}
render() {
return (
<Provider value={this.state.currentUser}>
<UpdateBlocker>
<Consumer>
{currentUser => <p>The current user is {currentUser.name}</p>}
</Consumer>
</UpdateBlocker>
</Provider>
);
}
}
Enjoy!
react-broadcast is developed and maintained by React Training. If you're interested in learning more about what React can do for your company, please get in touch!
FAQs
Reliably communicate state changes to deeply nested React elements
We found that react-broadcast demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.