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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@ryvora/react-portal

v2.0.0

Published

🚪✨ Render React components outside their parent DOM hierarchy. Perfect for modals and overlays!

Readme

Portal 🚪✨

Greetings, DOM Teleporter! 🧙‍♀️

The portal module provides a Portal component that lets you render children into a different part of the DOM tree, outside of their parent component's DOM hierarchy. This is super useful for things like modals, tooltips, and dropdown menus that need to appear on top of everything else or escape an overflow: hidden parent.

It's like having a magic door in your component that leads anywhere in the DOM! 🌌

Why Use Portals?

  • Stacking Context: To avoid z-index issues and ensure your component appears on top.
  • Overflow: To break out of a parent container that has overflow: hidden or other restrictive styles.
  • Accessibility: For modals, it's common to portal them to the end of document.body to manage focus and ARIA attributes correctly.

Basic Usage

import { Portal } from '@ryvora/react-portal';
import React, { useState } from 'react';

function MyModal() {
  const [isOpen, setIsOpen] = useState(false);

  return (
    <>
      <button onClick={() => setIsOpen(true)}>Open Modal</button>
      {isOpen && (
        <Portal container={document.body}>
          {' '}
          {/* Optional: defaults to document.body */}
          <div className="my-modal-overlay">
            <div className="my-modal-content">
              <h2>I am a Portalled Modal!</h2>
              <button onClick={() => setIsOpen(false)}>Close</button>
            </div>
          </div>
        </Portal>
      )}
    </>
  );
}

Teleport your components to where they need to be! 슝! (Swoosh!) 💨