All Versions
92
Latest Version
Avg Release Cycle
59 days
Latest Release
642 days ago

Changelog History
Page 1

  • v0.39.1

    February 08, 2018
    • Rem @providesModule from copied warning.js which can cause issues with Flow/RN.
  • v0.39.0

    September 26, 2017
    • React 16 support.
      • Note: React 16 inverts the call order of setState(obj, cb). Parent components' callbacks are now called first, where they previously were last.
  • v0.38.0

    September 13, 2017
    • Bugfix: Don't drop querystring from <CaptureClicks>.
  • v0.37.0

    April 29, 2017
    • Import create-react-class and prop-types to deal with React 15.5 warnings. Thanks @curquhart
  • v0.36.5

    February 27, 2017
    • Fix a few unknown props errors. Thanks @BlakeRxxk. Ref: #178, #181
    • Update dev dependencies.
  • v0.36.4

    January 23, 2017
    • Add the ability to decode named segments in routes before they are given as props to handlers. See the url pattern docs.
  • v0.36.3

    December 08, 2016
    • Reduce npm tarball size by 80% (excluding docs, examples, etc)
  • v0.36.2

    December 08, 2016
    • Remove usage of React.DOM.*, which will soon be deprecated in React 16 and has incompatibilities with Preact, Inferno, etc.
  • v0.36.1

    December 08, 2016
    • 🛠 Fix component propType. Thanks @jsg2021.
  • v0.36.0

    December 08, 2016
    • 🛠 Router: Avoid unnecessary setPath() calls when receiving identical props. Fixes #177
    • CaptureClicks: Potentially breaking change:
      • Previously, <CaptureClicks> would call props.gotoURL() (default: window.location.href = e.href) as soon
        as the first router failed to match. This was error-prone as it depended on the registration order of routers.
        Subrouters with limited routes could cause navigation not to occur.
      • This was masked somewhat by the extraenous setPath() calls. Navigation would occur, but onNavigation would
        not fire.
      • Now, <CaptureClicks> calls props.gotoURL() only if all routers fail to match.