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

use-imperative-portal

v0.2.1

Published

Imperative React hooks for Portals

Downloads

8

Readme

use-imperative-portal

version mingzip size license

Imperative React hooks for Portals

  • React >=18
  • Supports React Native

Example

import { useImperativePortal } from 'use-imperative-portal'

function Demo() {
    const openPortal = useImperativePortal()

    async function onClick() {
        const portal = openPortal((text = 'loading...') => (
            <Modal
                onRequestClose={() => {
                    portal.close() // 👈 Modal will be closed.
                }}
            >
                {text}
            </Modal>
        ))

        await asyncJob()

        if (portal.isClosed) {
            return
        }

        portal.update('updated!') // 👉 Modal changes from "loading ..." to "updated!"
    }

    return <button onClick={onClick}>Open!</button>
}

See a Demo.

Getting Started

Install the package in your project.

npm install use-imperative-portal

Wrap the root component with PortalProvider.

import { PortalProvider } from 'use-imperative-portal'

ReactDOM.createRoot(document.getElementById('root')).render(
    <PortalProvider>
        <App />
    </PortalProvider>
)

The ReactNode passed through the portal is added behind the children of PortalProvider.

function App() {
    const openPortal = useImperativePortal()

    useEffect(() => {
        const portal1 = openPortal(<p>bbb</p>)
        const portal2 = openPortal(<p>ccc</p>)

        // ...
    }, [])

    return <div>aaa</div>
}

Output

<div>aaa</div>
<p>bbb</p>
<p>ccc</p>

API

useImperativePortal()

This is a React hooks that returns the openPortal() function.

import { useImperativePortal } from 'use-imperative-portal'

function App() {
    const openPortal = useImperativePortal()

    // ...
}

openPortal(node)

This function render the ReactNode argument to the endpoint of the portal. And returns the imperative portal object.

function onPopupOpenerClick() {
    const portal = openPortal(<Popup onClose={() => portal.close()} />)

    // ...
}

portal.update(...args)

When you open the portal, you can use a function instead of ReactNode and can be updated later.

const portal = openPortal(({ title = 'Hi!', description = 'I luv you' } = {}) => (
    <section>
        <h3>{title}</h3>
        <p>{description}</p>
    </section>
))

// ...

portal.update({
    title: 'Hello!',
    description: 'I like u',
})

If it is a render using a function, the default value of the argument for the initial rendering is required.

portal.close()

Close the portal and remove the rendered nodes.

portal.isClosed

This value is whether the portal is closed.

console.log(portal.isClosed) // => false

portal.close()

console.log(portal.isClosed) // => true

<PortalProvider />

This is a Provider component that shares the portal context.

import { PortalProvider } from 'use-imperative-portal'

// ...

root.render(
    <PortalProvider>
        <App />
    </PortalProvider>
)

providerProps.withEndpoint

If withEndpoint is false, the endpoint automatically specified in the provider will be disabled. The default is true.

<PortalProvider withEndpoint={false} />

This is useful when setting the endpoint directly.

<PortalEndpoint />

ReactNode, which is passed to the portal, is rendered to the place where this component is located. This is useful when you want to change the endpoint position.

import { PortalEndpoint, PortalProvider } from 'use-imperative-portal'

//...

root.render(
    <PortalProvider withEndpoint={false}>
        <div>
            <PortalEndpoint />
        </div>
        <App />
    </PortalProvider>
)

createPortalContext()

Create a new portal context. Instead of using the Default context, it is useful for developing apps by mixing multiple portals.

import { createPortalContext, useImperativePortal } from 'use-imperative-portal'

const modal = createPortalContext()
const toast = createPortalContext()

//...

root.render(
    <modal.Provider withEndpoint={false}>
        <toast.Provider>
            <div>
                <modal.Endpoint />
            </div>
            <App />
        </toast.Provider>
    </modal.Provider>
)

function App() {
    const openModalPortal = useImperativePortal(modal)
    const openToastPortal = useImperativePortal(toast)

    //...
}

License

MIT © skt-t1-byungi