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-optimistic-ui-hook

v1.0.8

Published

Minimal zero dependency optimistic UI pattern implementation with a React Hook

Downloads

15

Readme

NPM Build Status codecov David npm npm bundle size npm

react-optimistic-ui-hook

Minimal zero dependency "optimistic UI" pattern implementation in a React Hook.

What is "Optimistic UI"?

Optimistic UIs don’t wait for an operation to finish to update to the final state. They immediately switch to the final state, showing fake data for the time while the real operation is still in-progress. Read More Here

Note that you can search for "optimistic UI" and read more about this pattern and how it works. It simply lets your app looks faster by expecting a successful call to something like an API before getting the real response and update the interface based on that expectation.

Installation

Using NPM:

npm install react-optimistic-ui-hook

Using Yarn:

yarn add react-optimistic-ui-hook

Usage

import React from 'react'
import { useOptimisticUI } from 'react-optimistic-ui-hook'

const USERNAME = 'mamal72'
const PREDICTED_AVATAR_URL = 'https://avatars0.githubusercontent.com/u/810438?v=4'
const DELAY_IN_MS = 2000

async function getGithubAvatarURL(username: string): Promise<string> {
  const response = await fetch(`https://api.github.com/users/${username}`)
  const data = await response.json()

  return new Promise((resolve) => {
    setTimeout(() => {
      resolve(data.avatar_url)
    }, DELAY_IN_MS);
  })
}

export function GithubAvatar() {
  const { status, result, error } = useOptimisticUI<string>(() => getGithubAvatarURL(USERNAME), PREDICTED_AVATAR_URL)

  if (status === 'failed') {
    // The "result" will be the predicted image url passed to the Hook,
    // But "error" is set to the raised error in the passed promise
    console.error("Failed to fetch image!", error)
  }

  if (status === 'loading') {
    // The "result" will be the predicted image passed to the Hook again!
    console.log('Loading image!')
  }

  if (status === 'succeed') {
    // The "result" will be the resolved promise response here!
    console.log("Resolved image!", result)
  }

  return (
    <div>
      <img src={result} alt="avatar" />
      <p>Status: {status}</p>
    </div>
  )
}

Contribution

You can report bugs and issues here.

You can also send a PR if you feel like you can improve or fix something. Don't forget to write/update tests for your changes.