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

@initd.sg/await-promise

v1.0.0

Published

Async React component for awaiting a promise.

Downloads

2

Readme

await-promise ⌛

Async React component for awaiting a promise and passing its result to other components.

Why?

This library helps in fetching data from server component and pass it down to children components. Normally you would await the promise in the server component but this is bad since you have to wait every promises in order to paint something on the website. With this library, it will make the server component display immediately. This library also make use of Suspense where the component will show a fallback component while waiting for the component to resolve.

1. Install

yarn add @initd.sg/await-promise

2. Usage

To use just pass the promise to the fn props. <AwaitPromise /> children accepts a function with the argument being the result of the promise. With this method we can put a client component inside the <AwaitPromise /> and show a loading fallback while waiting for that promise to resolve.

import { AwaitPromise } from "await-promise";

export default function Page() {
    const fn = new Promise<{ name: string }>((resolve) =>
        setTimeout(() => resolve({ name: "user" }), 1000)
    );

    return (
        <>
            <AwaitPromise fallback={"loading..."} fn={fn}>
                {(user) => <div>{user.name}</div>}
            </AwaitPromise>
        </>
    );
}

3. Error Handling

A promise passed to fn argument may throw an error due to network error or incorrect http parameters when trying to call an external API. By default, <AwaitPromise /> handles this error by showing the error message. In case we want to customize the error message, we can just create another component and pass to the errorFallback props.

import { AwaitPromise } from "await-promise";

export default function Page() {
    const fn = new Promise<string>((resolve, reject) =>
        setTimeout(() => reject("Network Error Occured"), 1000)
    );

    return (
        <>
            <AwaitPromise 
                fallback={"loading..."}
                errorFallback={(err) => <ErrorText err={err} />} 
                fn={fn}
            >
                {(user) => <div>{user.name}</div>}
            </AwaitPromise>
        </>
    );
}

function ErrorText(err: Error) {
    console.error(err); // error logging
    return <p className="text-red-500">{err.message}</p>
}