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

@raid/hooks

v6.1.1

Published

React hooks to complement @raid

Downloads

6

Readme

@raid/hooks

React hooks that link in to raid signals and streams

npm License: MIT Build Status Coverage Status js-standard-style

Raid Documentation

Getting Started

Install with yarn or npm

yarn add raid @raid/hooks
npm i -S raid @raid/hooks

Raid helps to manage state throughout your application and these hooks help you to manage the signals and streams that raid exposes to allow your application to react to changes over time to that state.

Hooks

useSignal (supplied signal)

<Function {Raid.Signal, options:Object}> => { state:Object, emit: Function }

useSignal can attach to a signal and returns the state passing through the signal as well as an emit function to send messages to the signal.

const Posts = () => {
  const { state, emit } = useSignal(signal)

  return (
    <>
      {state.posts.map(post => <Post {...post} />)}
      <SubmitPost onSubmit={text => emit({ type: 'createPost', payload: text })}
    </>
  )
}

The useSignal hook also accepts an options argument:

options {
  selector: Function(state: Object)
}

A selector function can be used to transform the state coming out of the signal and supplying it in the return from the hook:

const Posts = () => {
  const { posts, emit } = useSignal(signal, {
    selector: state => filter(post => post.isSubmitted)(state.posts)
  })

  return (
    <>
      {posts.map(post => <Post {...post} />)}
      <SubmitPost onSubmit={text => emit({ type: 'createPost', payload: text })}
    </>
  )
}

The ‘supplied’ form of useSignal is where a signal is supplied as the first parameter. However, this parameter is optional and, if omitted, the hook will attempt to find a signal in context.

useSignal (context)

If the signal parameter is omitted then useSignal will attempt to find a signal from the context. You can place a signal into the context by using a SignalProvider:

const App = () => {
  return (
    <SignalProvider signal={signal}>
      <Posts />
    </Signal>
  )
}

The Provider form works in the same way as manually supplying a signal to the useSignal hook and outputs the state (after any transform by a selector function) and an emit function to send messages to the signal.

Running tests

$ yarn
$ yarn test

Contributing

Pull requests are always welcome, the project uses the standard code style. Please run yarn test to ensure all tests are passing and add tests for any new features or updates.

For bugs and feature requests, please create an issue.

See the root readme for more information about how the repository is structured.

License

MIT