Nacho Printing Machine


    0.2.1 • Public • Published


    Async declarative reactive component-based (and other buzzwords) programming made easy.

    Inspired by Relay. An attempt to create unified container solution.

    NB: For now Transmitter depends on Rx (used as peer dependency).


    The idea of transmitter for UI is heavily inspired by A Mathematical Theory of Communication.


    Install via NPM:

    npm install --save retransmitter

    Require the lib in your code:

    import Transmitter from 'retransmitter';

    Still using that old syntax?

    var Transmitter = require('retransmitter');

    NB: If you're NPM3 user please make sure you have these dependencies installed. I'll make these dependencies as own dependencies after NPM3 will be used widely.

    npm install --save react react-dom rx

    How it works

    Just combineLatest operator magic. See more on


    Transmitter.create(Component, options)

    • Component — React Component or enum {pending, success, failure} of React Components.
    • options — object with next definitions:
      • initialVariables (optional) — an object with predefined variables for fragments.
      • fragments — set of functions that are fetching data from different sources. Names should be the same as follow prop names in the component you're using.
      • shouldContainerUpdate() (optional) — lifecycle hook that receives new props and returns true or false.




    Creates an Observable from Store (Flux, Redux, etc). Store is an object that provides next API:

    • getState() — returns current state of this store.
    • subscribe() — adds a change listener and returns unsubscribe function.


    This method is not required for using. If you use native Promises you can just return them as fragment's result.

    See more in RxJS docs.


    Use if you want to pass dummy or constant data via fragment. If you want to pass event hook (ie Flux's Action Creator) you don't need to use fromValue.

    See more in RxJS docs.


    function Item({key, title, description}) {
        return (
                <p><a href={`/articles/${key}`}>Read more</a></p>
    function ItemsList({items = []}) {
        return (
                {{id, title, description}) =>
                    <Item key={id} title={title} description={description} />
    ItemsListContainer = Transmitter.create(ItemsList, {
        items() {
            return fetch('/items')
                .then(r => r.json());
    ReactDOM.render(<ItemsListContainer />, ...);

    Multiple choise component

    ItemsListContainer = Transmitter.create({
        pending: LoadingSpinner,
        success: ItemsList,
        failure: ItemsListError
    }, {
        items() {
            return fetch('/items')
                .then(r => r.json());
        query() {
            return Transmitter.fromStore(QueryStore);
        onSelect() {
            return ItemsActions.selectItem;
    --[items]-------------------------------|> (from items fragment)
    ------"query"----------"query2"---------|> (from query store)
    ------{items, query}---{items, query2}--|> (result that will be passed to ItemsList)

    When <ItemsListContainer /> is added to the view pending component will be rendered at first. pending component will be rendered with props:

    • onAbort — the callback that used as event hook and dispose all fragments fetching processes.

    After loading is finished success or failure component will be rendered (depends on results). failure component will receive next props:

    • error — the error instance that will be received in failed getter.
    • onRetry — the callback that can be attached as event hook and will restart data fetching.


    • Promises
    • Observables
    • Falcor (since it uses Promises and Observables)
    • Stores (Flux, Redux) (See Transmitter.fromStore())
    • CSP channels
    • Relay


    npm i retransmitter

    DownloadsWeekly Downloads






    Last publish


    • alexeyraspopov