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

v1.4.0

Published

Promise portals for React

Downloads

15

Readme

react-promiseportal

Promise portals for React

Installation

Using npm:

$ npm install react-promiseportal

Using yarn:

$ yarn add react-promiseportal

Then with a module bundler like webpack, use as you would anything else:

// Using ES6 Modules
import { usePromisePortal } from 'react-promiseportal';
// using CommonJS modules
const usePromisePortal = require('react-promiseportal').usePromisePortal;

Why?

Normally when managing a modal, or similar hierarchy agnostic elements, it is common practice to render these in the component, and control them with local boolean state.

For example:

// App.js
import React from 'react';

function App() {
  const [isOpen, setOpen] = React.useState(false);
  return (
    <>
      <button onClick={() => setOpen(true)}>Click me to open a modal</button>
      <SomeModalComponent open={isOpen}>
        <button
          onClick={() => {
            alert('You confirmed!');
            setOpen(false);
          }}
        >
          Confirm
        </button>
        <button
          onClick={() => {
            alert('You cancelled.');
            setOpen(false);
          }}
        >
          Cancel
        </button>
      </SomeModalComponent>
    </>
  );
}

In large components, managing several modals with different isOpen state can be confusing.
With react-promiseportal, I offer complete co-location.

Usage

At the top-level of your application, import the PromisePortalProvider module.

// AppContext.js
import React from 'react';
import { PromisePortalProvider } from 'react-promiseportal';

function AppContext() {
  return (
    <PromisePortalProvider>
      <App />
    </PromisePortalProvider>
  );
}

You can then import usePromisePortal (hook) or withPromisePortal (hoc).

// App.js
import React from 'react';
import { usePromisePortal } from 'react-promiseportal';

function App() {
  const portal = usePromisePortal();
  return (
    <button
      onClick={async () => {
        const didConfirm = await portal((onConfirm, onCancel) => {
          return (
            <SomeModalComponent open>
              <button onClick={onConfirm}>Confirm</button>
              <button onClick={onCancel}>Cancel</button>
            </SomeModalComponent>
          );
        });

        if (didConfirm) alert('You confirmed!');
        else alert('You cancelled.');
      }}
    >
      Click me to open a modal
    </button>
  );
}

Calling onConfirm with an Event or a falsy value, will resolve the promise with the value true.
If called with a truthy value, like an object, this is returned instead.

For example, if the Modal were instead a form, which returned some input for a request:

// App.js
import React from 'react';
import { usePromisePortal } from 'react-promiseportal';

function App() {
  const portal = usePromisePortal();
  return (
    <button
      onClick={async () => {
        // onConfirm is called with {potatoes: true}
        // So the promise is resolved with {potatoes: true}
        const input = await portal((onConfirm, onCancel) => {
          return (
            <SomeFormComponent open>
              <button onClick={() => onConfirm({ potatoes: true })}>
                Confirm
              </button>
              <button onClick={onCancel}>Cancel</button>
            </SomeFormComponent>
          );
        });

        if (input) fetch();
        else alert('You cancelled.');
      }}
    >
      Click me to open a modal
    </button>
  );
}

Credits

react-promiseportal is built and maintained by babangsund.
@blog.
@github.
@twitter.