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

@sunny-g/cycle-react-driver

v0.4.11

Published

(un)official React driver for Cycle.js

Downloads

17

Readme

cycle-react-driver

(un)official React driver for Cycle.js

why

React is a fantastic pseudo-functional view library that has a great community of useful third-party components. I wanted to use React (and eventually, all of it's various flavors) with Cycle.js without having to write a driver for each, so I wrote this simpler one instead!

Unlike the Cycle.js React Native driver, this driver does two much more basic things:

  1. provides callback handlers (for you to pass to your components as function props) and their matching streams via the React source
  2. subscribes to your React sink stream to render the virtual DOM tree

Enjoy!

installation

npm install --save @sunny-g/cycle-react-driver

usage

Basic usage with the Cycle.js counter example:

import makeReactDOMDriver from '@sunny-g/cycle-react-driver/es2015/dom';

function main(sources) {
  const incrementReducer$ = sources.REACT
    .event('increment')
    .map(_ => ({ count }) => ({
      count: count + 1
    }));

  const decrementReducer$ = sources.REACT
    .event('decrement')
    .map(_ => ({ count }) => ({
      count: count - 1
    }));

  const reducer$ = xs.merge(
    incrementReducer$,
    decrementReducer$
  );

  const props$ = reducer$
    .fold((state, reducer) => reducer(state), { count: initialCount });

  const decrementHandler = sources.REACT.handler('decrement');
  const incrementHandler = sources.REACT.handler('increment');

  // the sink is a stream of a rendered React elements
  const vtree$ = props$
    .map(({ count }) =>
      <div>
        <button
          key="decrement"
          onClick={decrementHandler}
        >
          Decrement
        </button>
        <button
          key="increment"
          onClick={incrementHandler}
        >
          Increment
        </button>
        <p>{`Counter: ${count}`}</p>
      </div>
    );

  return {
    REACT: vtree$,
  };
}

run(main, {
  REACT: makeReactDOMDriver('#main-container'),
});

api

makeReactDOMDriver

parameters:
  • domElement: Element: DOM element in which the root React component will be rendered

Example:

import makeReactDOMDriver from '@sunny-g/cycle-react-driver/es2015/dom';

run(main, {
  // ... other drivers
  REACT: makeReactDOMDriver(document.querySelector('#app-container')),
});

react source

react.select(selector: string | null): ReactSource

parameters:
  • selector: string | null: A key used to define the new ReactSource
returns:
  • ReactSource: A new ReactSource that defines it's own handler-event stream pairs

react.handler(key: string, withMemory?: boolean): (...args: any[]) => void

parameters:
  • key: string: Unique key for the handler-event stream pair
  • withMemory?: boolean = false: If the handler is called before the stream is used, set this to true for the stream to replay the last event to new subscribers; defaults to false
returns:
  • (...args: any[]) => void: Function that should passed down to a React element as an event handler

Example:

const onTextChange = sources.REACT.handler('onTextChange');

react.event(key: string, withMemory?: boolean): MemoryStream<any | any[]> | Stream<any | any[]>

parameters:
  • key: string: Unique key for the handler-event stream pair
  • withMemory?: boolean = false: If the handler is called before the stream is used, set this to true for the stream to replay the last event to new subscribers; defaults to false
returns:
  • Stream<any | any[]> | MemoryStream<any | any[]>: A stream that emits the value(s) given to the matching handler whenever the handler is invoked
    • NOTE: If the React element invokes the matching handler function with more than one argument, the stream will emit an Array of the arguments, rather than just the first argument - otherwise, the stream emits the single argument

Example:

// stream of text from the input box
const props$ = sources.REACT
  .event('onTextChange')         // same key as the handler defined earlier
  .map(([ event ]) => event)     // handler was invoked with multiple arguments, but we only want the first
  .map(e => e.target.value);

react sink: Stream<ReactElement<any>>

should return:
  • Stream<ReactElement<any>>: A stream of React elements

Example:

// `props$` and `onTextChange` defined earlier

return {
  // ... other sinks...
  REACT: props$.map(({ text }) => (
    <input
      type="text"
      value={text}
      onChange={onTextChange}
    />
  ))
};

helpers

fromReactDOMComponent(sinkName, ReactComponent) => CycleComponent

Creates a Cycle.js component from a ReactDOM component

parameters:
  • sinkName: string: Name of the sink you want to assign the React element stream to
  • ReactComponent: The raw React component, pure or stateful
returns:
  • CycleComponent: A Cycle.js component that takes in sources (in particular, a React source provided by cycle-reactdom-driver and a props source that passes in desired props) and returns sinks (in particular, a React sink of React elements)

Example:

import { fromReactDOMComponent } from '@sunny-g/cycle-react-driver/es2015/dom';

const View = props => (
  <input
    type="text"
    value={props.text}
    onChange={props.onTextChange}
  />
);

const CycleViewComponent = fromReactDOMComponent('REACT', View);

toReactDOMComponent(sinkName, CycleComponent) => ReactComponent (EXPERIMENTAL)

Creates a ReactDOM component from a Cycle.js component

parameters:
  • sinkName: string: Name of the sink containing the React element stream
  • CycleComponent: A Cycle component
    • NOTE: Since the Cycle component is not (currently) run within the React component, the Cycle component should only take in a ReactDOM and props source and return only a ReactDOMDriver sink
returns:
  • ReactDOMComponent: A normal React DOM class component

Example:

import { toReactDOMComponent } from '@sunny-g/cycle-react-driver/es2015/dom';

const CycleViewComponent = (sources) => ({
  REACT: sources.props.map(props =>
    <input
      type="text"
      value={props.text}
      onChange={props.onTextChange}
    />
  ),
});

const ReactComponent = toReactDOMComponent('REACT', CycleViewComponent);

// then, it can be used as such:
<ReactComponent
  text={"sample text"}
  onTextChange={textChangeHandler}
/>

contributing

todo

  • add testing mock source
  • explain contribution process
  • add more tests :)
  • add more drivers for more React libs
  • explain why I wrote this

license

ISC