npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

react-global-component-stack

v1.0.0

Published

Sometimes you have a single component on a page, but you want to be able to modify it from other components. You could hoist your state, and pass down some updater functions with context. However, this takes a different approach, based of React Native's `

Downloads

3

Readme

React Global Component Stack

Sometimes you have a single component on a page, but you want to be able to modify it from other components. You could hoist your state, and pass down some updater functions with context. However, this takes a different approach, based of React Native's StatusBar component.

React Native has a <StatusBar /> component. This component doesn't actually render anything, but what it does do is update the props of the status bar. To turn hide existing status bar, you just render <StatusBar hidden />.

You can render as many of these as you want, and the last rendered status bar "wins". Their props are actually merged, you don't have to keep track of all the other components.

Let's say we want to set the title of a web page. A naïve implementation could look like this,

class Title extends Component {
  componentDidMount() {
    document.title = this.props.title;
  }

  componentDidUnmount() {
    // What do we do here?
  }

  render() {
    return null;
  }
}

We can implement the same with this library.

import globalComponentStack from "react-global-component-stack";

const Title = globalComponentStack({ title: "" }, props => {
  document.title = props.title;
});

The first argument is the default props, and the second is a function that is run whenever the props change. The function is actually called with (currentProps, previousProps), so you can be more efficient about updates.

Say we want to implement a way to hide the home indicator on the new iPhone X. We can implement some native code that can toggle it, and expose a component as so.

const HomeIndicator = globalComponentStack(
  { hidden: false },
  (props, prevProps) => {
    if (props.hidden !== prevProps.hidden) {
      NativeCode.HomeIndicatorManager.setHidden(props.hidden);
    }
  }
);

If we have an actual React component that we want to render based on the merged props, that's possible too.

let delegate;
const defaultState = { inverted: false };

const NavBar = globalComponentStack(defaultState, props => {
  if (delegate != null) {
    delegate.setState({ inverted: props.inverted });
  }
});

class NavBarComponent extends Component {
  constructor() {
    super();
    delegate = this;
    this.state = defaultState;
  }

  render() {
    const { inverted } = this.state;
    return <your-markup />;
  }
}

This obviously can't be used everywhere, but it can be really handy in places.