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

v2.0.0

Published

A simple component used for rendering collections and arrays.

Downloads

4

Readme

react-each NPM Package

ISC License

A simple React component used for rendering collections and arrays.

When you see this component, you may be asking "Why did you make this? You can just use the 'map' function of your item array!". So, here are the reasons that you might use this component instead of the map function:

  • Since you're using a component, you can "connect" it using connect from the redux-react library.
  • You have the ability to cleanly implement rendering when the items array is either not defined or empty (see else prop below).
  • You may find that your JSX code is more clean and easier to read (though, I would recommend using map if you don't need this for the first two reasons that have been listed for efficiency reasons).

Storybook

Changelog

Install

$ npm i --save react-each

Usage

import React from 'react';
import Each from 'react-each';


export default function MyComponent(props) {
  return (
    {/* ... */}

      <Each items={props.items} renderItem={(item, index, { itemsLastIndex }, items) => (
        // Render item...
      )} else={() => (
        // Render component(s) when list is not defined or is empty...
      )} />

    {/* ... */}
  );
}

Props

  • items ?(Array|Function)

    Array of items (or function which returns an array of items) to use for rendering.

  • renderItem !Function - REQUIRED

    Render function called for each item found in the given items array.

  • else ?Function

    Render function called when items array is not defined or is empty.

  • startIndex ?Number (Default: 0)

    Index to start at (inclusively) when rendering items (all items that come before startIndex will not be rendered).

  • endIndex ?Number (Default: (items.length - 1))

    Index to end at (inclusively) when rendering items (all items that come after endIndex will not be rendered).

License

ISC License (ISC)

Copyright (c) 2019, Brandon D. Sara (http://bsara.pro/)

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.