FaCC maybe worth considering instead of context types

[rmoorman]

Instead of using the context feature of react to pass through data to the timer rendering component, this could also be achieved using a function as child component style API.

Using the example given within the readme, this:

const Countdown = (props, context) => {
  const d = new Date(context.remaining);
  const { seconds, milliseconds } = {
    seconds: d.getUTCSeconds(),
    milliseconds: d.getUTCMilliseconds(),
  };
  return (
    <p>{`${seconds}.${milliseconds}`}</p>
  );
};

Countdown.contextTypes = {
  remaining: PropTypes.number,
};

<Timer remaining={20000}>
  <Countdown />
</Timer>

could become something like this:

const Countdown = ({remaining}) => {
  const d = new Date(remaining);
  const { seconds, milliseconds } = {
    seconds: d.getUTCSeconds(),
    milliseconds: d.getUTCMilliseconds(),
  };
  return (
    <p>{`${seconds}.${milliseconds}`}</p>
  );
}

<Timer remaining={20000}>
  {remaining => <Countdown remaining={remaining} />}
</Timer>

This is a pattern also used by react-motion for example and what appeals to me personally is, that the data flow is a bit more explicit this way IMHO. (Of course there are a lot of differing opinions on this one, but in case you deem it useful ...)