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

v2.1.0

Published

Spooky action at a distance

Downloads

20

Readme

Build Status npm version js-standard-style

Scatter a component from your main React rendering tree and render it as an entangled component somewhere else.

Its main goal it to allow the application state to live in a centralized location while components can be rendered somewhere else (iframes, separate tabs).

Installation

Install the npm package:

npm install react-entanglement

API

Entanglement

This components setup the infrastructure that allows a component in its children tree to be scattered to a separated entangled tree.

Entanglement between the two rendering trees is achieved by using a proper adapter. A default Entanglement.passthroughAdapter implementation is provided; it can be used if entanglement is to be achieved in the same window.

Using that adapter a simple implementation would be:

import React from 'react'
import { render } from 'react-dom'

import Entanglement from 'react-entanglement'

render((
  <Entanglement adapter={Entanglement.passthroughAdapter()}>
    { /* any children component here can be scattered */ }
  </Entanglement>
), document.getElementById('app'))

Entanglement.scatter

Once the basic communication and entanglement is setup, we can start scattering components. So imagine you have an application with a dialog that is normaly render as:

import React from 'react'
import { render } from 'react-dom'

import Entanglement from 'react-entanglement'

render((
  <Entanglement adapter={Entanglement.passthroughAdapter()}>
    <Dialog
      onClick={(value, number) => window.alert('clicked' + value + number)}
      items={['one', 'two', 'three']}
    />
  </Entanglement>
), document.getElementById('app'))

The only change we need to do to allow this component to be rendered is create a scattered version of it:

const ScatteredDialog = Entanglement.scatter({ name: 'Dialog' })

And render that instead of the real component:

<Entanglement adapter={Entanglement.passthroughAdapter()}>
  <ScatteredDialog
    onClick={(value, number) => window.alert('clicked' + value + number)}
    items={['one', 'two', 'three']}
  />
</Entanglement>

Entanglement.materialize

Given there is a scattered component, we can create an entanglement in a separated rendered tree and materialize the component:

import React from 'react'
import { render } from 'react-dom'
import Entanglement from 'react-entanglement'
import Dialog from './dialog'

const MaterializedDialog = Entanglement.materialize({ name: 'Dialog', constructor: Dialog })

render((
  <Entanglement adapter={Entanglement.passthroughAdapter()}>
    <MaterializedDialog />
  </Entanglement>
), document.getElementById('remote-app'))

React Context

Entanglement also has support to context props, but you need to explicitly define which contextTypes to scatter and materialize while defining the components.

Just add an extra contextTypes option while defining the Entanglement components, example:

Entanglement.scatter({ contextTypes: { color: React.PropTypes.string }, name: 'Dialog' })
Entanglement.materialize({ contextTypes: { color: React.PropTypes.string }, name: 'Dialog', constructor: Dialog })

Adapters

The adapter signature should be:

const adapter = {
  scatterer: {
    unmount: (componentName) => {},
    render: (componentName, data, handlerNames, context) => {},
    addHandlerListener: (componentName, handlerName, cb) => {}
  },

  materializer: {
    addUnmountListener: (componentName, cb) => {},
    addRenderListener: (componentName, cb) => {},
    handle: (componentName, handlerName, args) => {}
  }
}

You can check the default passthroughAdapter as a reference implementation.

The methods addHandlerListener, addUnmountListener and addRenderListener must return a function that can be used to dismiss the listener that was configured using the passed cb.

Development

To try it out locally and help development, start the local server:

npm start

And open:

Or run the unit tests:

npm test

Kudos

Acknowledgements

  • The react-entanglement logo is a derivative from the React logo.