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-composed

v0.0.2

Published

Compose react render props

Downloads

2

Readme

Compose React components with render props

React-composed makes code where you need to get the result of multiple components with render props easier and more readable.

How does it work:

// you might have these two components
const Test1 = ({ children }) => children("Test1");
const Test2 = ({ children }) => children("Test2");

// if you would need both results you would compose them like this:

<Test1>
  {test1 =>
    <Test2>
      {test2 =>
        <p>test1: {test1}, test2: {test2}</p>
      }
    </Test2>
  }
</Test1>

// with react-composed this would look like the following:
import Composed from 'react-composed'

<Composed test1={<Test1/>} test2={<Test2/>}>
  {({test1, test2}) => <p>test1: {test1}, test2: {test2}</p>}
</Composed>

With react-composed you need less nesting. With more API choosing for render-props, instead of HOCs, you'll have more and more components passing information down using render props. For instance react apollo:

<Composed 
  query1={<Query query={query1}} 
  query2={<Query query={query2}} 
  mutation={<Mutation mutation={mutation}}
>
  {({query1, query2, mutation}) => <Component {...} />}
</Composed>

Requirements

react-composed only works with components that adopt the children prop as the primary render prop. Most React components use this convention now (even the official context API uses this)

Installation

Just yarn add react-composed