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

@lauf/store-react

v2.0.0

Published

Update React components when @lauf/store state changes

Downloads

53

Readme

Store bindings for React

Enables React apps to use @lauf/store for state-management

Read the API Reference or the reference usages below.

Usage

Track a part of Store state

// given some example store
interface CounterState {
  counter: number;
  active: boolean;
}
const counterStore = createStore<CounterState>({ counter: 0, active: false });

// bind Display to just the `counter` property
// won't re-render when `active` property changes
export const Display = (props: { store: Store<CounterState> }) => {
  const counter = useSelected(props.store, (state) => state.counter);
  return <h1>Counter is {counter}</h1>;
};

Getting Started

Install

npm install @lauf/store-react

Advanced

Create a store in a component

// create a store for the lifetime of this component
const store = useStore<CounterState>({ counter: 0, active: false });

A Store created through useStore can be passed through prop drilling or Context to descendant components, who will subscribe to the parts they want to track.

Note, using the useStore hook can often be avoided. A Store can be a singleton in most apps meaning a single instance can simply be created and exported from a module.

If you are certain that an ancestor React component will never be replaced and (hence) lose its state, then useStore can be used safely.

If you want different parts of the render tree to have their own independent copy of some Store, it offers the convenience of components simply creating their own Stores inline.

Consume the whole state

const rootState = useRootState(props.store);

Note, this is rarely needed in production code for several reasons...

  • well-architected business logic should live outside the render loop, using followSelector(...) from @lauf/store-follow
  • to consume part of the state, prefer {@link useSelector} which doesn't trigger renders on every state change
// Re-runs this functional component when any state changes
export const StateLog = (props: { store: Store<CounterState> }) => {
  const rootState = useRootState(props.store);
  const [stateHistory, setStateHistory] = useState<CounterState[]>([]);
  useEffect(() => {
    setStateHistory([...stateHistory, rootState]);
  }, [rootState]);
  return <h1>Counter is {counter}</h1>;
};