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

@antivixen/react-if-else

v0.0.6

Published

React JS library for the conditional rendering

Downloads

42

Readme

React If Else

Classical If/Else statement solution for the conditional rendering in React JS.

Usage

import { ConditionalView, If, Else } from "@antivixen/react-if-else";

export const BasicExample = () => {
  const { isLoading, isError, data } = getAsyncData();
  return (
    <>
      <h1>Our data</h1>
      <ConditionalView>
        <If when={isLoading}>
          <h2>Loading..</h2>
        </If>
        <If when={isError}>
          <h2>Error</h2>
        </If>
        <Else>
          <div>{data}</div>
        </Else>
      </ConditionalView>
    </>
  );
};

Why?

Why, you might ask? Well, as we can observe from the given example, it's quite evident that the state aligns with the rendered hierarchy. Another option could be:

export const PureExample = () => {
  const { isLoading, isError, data } = getAsyncData();
  return (
    <>
      <h1>Our data</h1>
      {isLoading ? (
        <h2>Loading</h2>
      ) : isError ? (
        <h2>Error</h2>
      ) : (
        <dic>{data}</dic>
      )}
    </>
  );
};

To adopt a cleaner code approach, you should elevate the static data title and eliminate the redundant and overly complex ternary operator. i

export const PureAdvancedExample = () => {
  const { isLoading, isError, data } = getAsyncData();

  if (isLoading) {
    return (
      <TitleContainer>
        <h1>Loading..</h1>
      </TitleContainer>
    );
  }

  if (isError) {
    return (
      <TitleContainer>
        <h1>Erorr</h1>
      </TitleContainer>
    );
  }

  return (
    <TitleContainer>
      <dic>{data}</dic>
    </TitleContainer>
  );
};

This not only appears significantly more verbose but also compels us to divide the view into two parts, resulting in the creation of more abstract layers.

react-if-else is better to be used for complex if/else rendering scenarios. If you need a solution to show/hide elements based on dynamic values, you should probably investigate this library