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

portals-component

v0.0.5

Published

this is library for portals components for React.js

Readme

portals-component

MIT License Maintainability npm version Codacy Badge
this is utility for portals api for React.js.

Problem

Have you ever come across problem which to use React.js partially? If so, you might have stribed to use React.js because you might have to ReactDOM.render() multiple times. but if you don't twist your idea, you can't pass state data to other area of ReactDOM.render() . If it's over middle apps, that's would be harder.

Resolution

parhaps, you might have read this official document. So, resolution is to use portals API!

This library is using portals API internally. if you use portals-component, this means you use portals api internal of this library.

Why not just use it?

that's because I wanted to assemble as a utility. I was faced situations which I have to use portals in production. First, I used ReactDOM.render multiple times, but I realized I can't pass state to other ReactDOM.render() area. I didn't care of it for a long time like 2 or 3 month. but one day, I was faced problem which I had to pass state to ReactDOM.render area to different ReactDOM.render .

At the same time, Facebook published portals App, so I decided to use it. after that I came up with idea of this library of base.

Props

| Name | Type | Default | Description | | --- | --- | --- | --- | | el | string | '' | dom element which is rendered. | | children | node | null | react element, you can use like this.props.children . | | dom | string | div | wrapper dom element. when you render DOM through using portals api, you have to specify dom element. |

Example

Let's say, you have a html file like below.

<html>
<head>
  <title>portals component</title>
</head>
<body>
  <div id="app"></div>
  <div id="portals-test"></div>
  <script src="./index.js"></script>
</body>
</html>

then, you can use portals-component like below.

import React from 'react';
import { render } from 'react-dom';
import PortalsComponent from '../lib';

const App = () => (
  <div>
    <PortalsComponent el="#portals-test">
      <div>app</div>
    </PortalsComponent>
    <div>different</div>
  </div>
)

render(<App />, document.getElementById('app'))

then, you can check dom which is rendered by using inspector like Google chrome. id app will be rendered like below.

<div>
  <div>different</div>
</div>

and inside of id portals-test is like below

<div>
  <div>app</div>
</div>