# react-through

> Declarative data mapping through react tree

Latest version **1.1.4** (published 2019-08-20) · MIT license · 0 weekly downloads

## Install

```sh
npm install react-through
pnpm add react-through
yarn add react-through
bun add react-through
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 1.1.4 |
| Published | 2019-08-20 |
| First published | 2017-12-14 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Unpacked size | 691.6 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 14 |
| Author | Serguei Okladnikov |
| Maintainers | oklas |
| Keywords | react, through, declarative, props, data, transfer, mapping, exchange |

## Links

- npm: https://www.npmjs.com/package/react-through
- Repository: https://github.com/oklas/react-through
- Issues: https://github.com/oklas/react-through/issues
- npm.io page: https://npm.io/package/react-through

## Alternatives

- [mobx-react](https://npm.io/package/mobx-react.md) — 2.8M weekly downloads
- [rc-tree](https://npm.io/package/rc-tree.md) — 2.6M weekly downloads
- [@react-oauth/google](https://npm.io/package/@react-oauth/google.md) — 1.3M weekly downloads
- [@wagmi/connectors](https://npm.io/package/@wagmi/connectors.md) — 877.0K weekly downloads
- [vee-validate](https://npm.io/package/vee-validate.md) — 836.4K weekly downloads

## Recent versions

- 1.1.4 (latest) — 2019-08-20
- 1.1.3 — 2019-02-13
- 1.1.2 — 2019-02-13
- 1.1.1 — 2018-06-14
- 1.1.0 — 2018-05-11
- 1.0.5 — 2018-04-16
- 1.0.4 — 2018-04-16
- 1.0.3 — 2018-01-05
- 1.0.2 — 2017-12-16
- 1.0.1 — 2017-12-14

## README

# react-through

## Declarative data mapping through react tree

**Extremal flexible and effective way to communicate between components.**

This library provides tools to map props directly from one component to another.
Source component may be specified in one place of react tree and destination
component which receives that props in another place of react tree.

This allows to create `agent` component (or set of agents) which maps some of
its props to named area and also allows to create `container` (or set of
containers) of that area from which that props are received.

And then all what you need is just to instantiate one or more created
`through-container` in one place(s) and specify some props for it in one or more
`through-agent` in another place(s) of react tree.

[![Npm package](https://img.shields.io/npm/v/react-through.svg?style=flat)](https://npmjs.com/package/react-through)
[![Npm downloads](https://img.shields.io/npm/dm/react-through.svg?style=flat)](https://npmjs.com/package/react-through)
[![Travis build status](http://img.shields.io/travis/oklas/react-through.svg?style=flat)](https://travis-ci.org/oklas/react-through)
[![Test Coverage](https://img.shields.io/codecov/c/github/oklas/react-through.svg)](https://codecov.io/gh/oklas/react-through)
[![Dependency Status](https://david-dm.org/oklas/react-through.svg)](https://david-dm.org/oklas/react-through)


***

Read the **[Documentation](https://react-through.js.org/basics/installation-and-setup)**

# Synopsis

``` javascript
  const Header = () => (
    Your ballance: <IndicatorContainer/> USD
  )

  const Content = () => (
    <IndicatorAgent balance=1000 />
  )

  <App>
    <Header />
    <Content />
  </App>
```


## LICENSE

#### [MIT](./LICENSE.md)

---
_Source: https://npm.io/package/react-through · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._
