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

@mariosant/react-cond

v0.1.3

Published

Create components based on conditions, with ease

Downloads

2

Readme

React Cond

Create components based on conditions, with ease.

NPM version CircleCI

Installation

Add @mariosant/react-cond to your package.json.

$ npm install @mariosant/react-cond

You can now import the module and use it like

import cond from '@mariosant/react-cond';

// Components
const Pending = () => 'Loading. Please wait...';
const NonIdeal = () => 'It seems there is an error!';
const Component = ({data}) => `This is the actual data: ${data}`;

// Predicates
const isPending = ({pending}) => pending;
const hasError = ({error}) => error;
const isOk = ({error, pending, data}) => !error && !pending && data;

// Final complex component
export const ComplexComponent = cond(
	[isPending, Pending],
	[hasError, NonIdeal],
	[isOk, Component],
	NonIdeal,
);

Usage

The package exports two main components you can use.

import cond, {hoc} from '@mariosant/react-cond';

The cond function takes a list of predicates and a default component if everything else fails.

const CommentsList = cond(
	[isPending, Pending], // Will render Pending if isPending returns true.
	[hasError, NonIdeal], // Will render NonIdeal if hasError returns true.
	[isOk, Component], // Will render Component if isOk returns true.
	NonIdeal, // If everything above fails, NonIdeal component will be rendered instead.
);

A predicate is a function. It will receive props and if it returns a truthy result, the associated component will be rendered.

For example,

import cond from '@mariosant/react-cond'

const isPending = ({pending}) => pending;
const Pending = () => <div>'Loading. Please wait.'</div>;

return cond(
	[isPending, Pending],
	...
);

For the developer's ease, a high order component version has been included. It can be easily combined with Recompose's compose.

import {hoc as cond} from '@mariosant/react-cond';
import {compose, withProps} from 'recompose';

return compose(
	withProps({something: true}),
	cond([isPending, Pending], [isOk, Component]),
)(DefaultComponent);

Meta

Marios Antonoudiou – @marios_ant[email protected]

Distributed under the MIT license.

https://github.com/mariosant/react-cond

Contributing

  1. Fork it (https://github.com/mariosant/react-cond/fork)
  2. Create your feature branch (git checkout -b feature/fooBar)
  3. Commit your changes using a semantic commit message.
  4. Push to the branch (git push origin feature/fooBar)
  5. Create a new Pull Request